CVE-2022-34910VulnerabilityPublished 27 Feb 2023Updated 30 May 2025

CVE-2022-34910: n/a

Source CVE Database V5

Not known to be exploited · CVSS 4.1 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

4.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AC:H/AV:L/A:N/C:H/I:N/PR:H/S:U/UI:N

Attack Complexity: High
Attack Vector: Local
Availability: None
Confidentiality: High
Integrity: None
Privileges Required: High
Scope: Unchanged
User Interaction: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Availability: None: There is no impact to availability within the impacted component.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Feb 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
n/a n/a	Affected =1.5.0	Fixed in–

AI-suggested

European organizations should implement several targeted mitigation strategies beyond generic advice: 1) Avoid using or deploying the vulnerable version (1.5.0) of the A4N application until a patched version is available. 2) Enforce strict device access controls, including strong authentication and encryption, to prevent unauthorized local access. 3) Limit device sharing among multiple users to reduce exposure risk. 4) Educate users about the risks of storing sensitive credentials on shared devices and encourage the use of unique, strong passwords to minimize damage from credential compromise. 5) Employ mobile device management (MDM) solutions to monitor and control application usage and enforce security policies. 6) Where possible, request or develop application updates that implement secure credential storage using Android's Keystore or encrypted databases. 7) Conduct regular audits of devices for unauthorized access or suspicious activity. 8) Encourage multi-factor authentication (MFA) for accounts accessed via the application to mitigate risks from password disclosure.

Description

An issue was discovered in the A4N (Aremis 4 Nomad) application 1.5.0 for Android. It uses a local database to store data and accounts. However, the password is stored in cleartext. Therefore, an attacker can retrieve the passwords of other users that used the same device.

Impact

For European organizations, especially those whose employees or users utilize the A4N Android application on shared or corporate devices, this vulnerability poses a risk of credential compromise. Attackers with access to a device could extract stored passwords, potentially leading to unauthorized access to user accounts within the application or related systems if password reuse occurs. Although the vulnerability requires local access and elevated privileges, the risk increases in environments where devices are shared, lost, or stolen. This could lead to data breaches, unauthorized data access, and potential lateral movement within organizational networks if credentials are reused. The confidentiality of user credentials is directly impacted, which can undermine trust in the application and the organization's security posture. However, since the vulnerability does not affect data integrity or availability, the immediate operational impact is limited to information disclosure. The medium severity indicates that while exploitation is not trivial, the consequences of successful exploitation warrant attention, particularly in sectors handling sensitive or regulated data.

CWE-312Cleartext Storage of Sensitive Information (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
Implementation · System Configuration · Operation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest.
Implementation · System Configuration · Operation
In some systems/environments such as cloud, the use of "double encryption" (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
Attack patterns
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 15:42 UTC

WeaknessesCWE-312

Technical details

References

Community reviews

Related threats