dbcve.org
Aremis 4 NomadsApplication · Aremis

CVE-2022-34910

MEDIUM · 5.5 CVSS v3.1 Published 2023-02-27
Fix available
A fix is available. Upgrade to 1.5.1 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The A4N (Aremis 4 Nomad) Android application version 1.5.0 stores user credentials in cleartext within a local SQLite database. Any attacker with physical access to the device or the ability to extract the database file can directly read all stored passwords without any cryptographic protection.

MitigationReplace cleartext password storage with salted hashing algorithms (e.g., bcrypt, PBKDF2, or Argon2) before storing credentials. If reversible encryption is required for business reasons, use Android Keystore to protect encryption keys.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Aremis 4 NomadsApplication
Affected:< 1.5.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Aremis 4 Nomad app is installed
    Use Android settings or adb to list installed packages and locate the Aremis 4 Nomad application, then retrieve its version number from the package manager
    Affected if The app is installed and its version is below 1.5.1 (the fixed version)
  2. Locate the application's database directory
    Access the app's private data directory (typically /data/data/<package_name>/databases/ or /data/user/0/<package_name>/databases/) via adb with root privileges or through a rooted device
    Affected if The database directory exists and contains SQLite database files
  3. Identify the SQLite database containing credentials
    List and examine the database files in the app's databases directory, looking for files that may contain user data or authentication-related tables
    Affected if A database file is found that stores user authentication information
  4. Inspect stored credentials for cleartext passwords
    Use sqlite3 or a database viewer tool to open the database and query tables that store user credentials. Examine the stored values to determine if passwords are stored in plaintext rather than being hashed or encrypted
    Affected if User credentials (passwords) are stored in readable, unhashed, unencrypted form in the database

A user is affected if the Aremis 4 Nomad app version is below 1.5.1 AND the application stores user passwords in cleartext within its SQLite database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.5.1 or later
Fixed in 1.5.1
Interim mitigation

Replace cleartext password storage with salted hashing algorithms (e.g., bcrypt, PBKDF2, or Argon2) before storing credentials. If reversible encryption is required for business reasons, use Android Keystore to protect encryption keys.

Recommended fix Moderate confidence

Aremis 4 Nomads version 1.5.1

  1. Upgrade the Aremis 4 Nomads (A4N) Android application to version 1.5.1 or later
  2. After upgrading, verify that passwords are no longer stored in cleartext in the local database
  3. Ensure all users on shared devices change their passwords after the upgrade to ensure credentials are re-encrypted with the secure storage mechanism

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aremis 4 Nomads Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34910 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34910 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data