dbcve.org
Aremis 4 NomadsApplication · Aremis

CVE-2022-34909

CRITICAL · 9.1 CVSS v3.1 Published 2023-02-27
Fix available
A fix is available. Upgrade to 1.5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 allows SQL Injection, by which an attacker can bypass authentication and retrieve data that is stored in the database.

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 · moderate confidence

SQL Injection vulnerability in the A4N (Aremis 4 Nomad) Android application version 1.5.0 allows remote attackers to bypass authentication mechanisms and execute arbitrary SQL queries against the application's backend database. The vulnerability stems from insufficient input sanitization in user-supplied fields, likely in login or data submission functions, enabling attackers to manipulate SQL statements to gain unauthorized access and exfiltrate sensitive data.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements in all database interactions, implement strict input validation and sanitization on the client and server side, and apply principle of least privilege to database accounts. Update to the latest patched version of the application when available.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Locate the Aremis 4 Nomad application
    Open the Android device Settings, navigate to Apps or Applications, and search for 'Aremis 4 Nomad', 'A4N', or 'Nomad' in the installed applications list
    Affected if The application is installed on the device
  2. Determine the installed application version
    In the Apps list, tap on the Aremis 4 Nomad entry and view the Version information displayed under the app name or in the App info screen
    Affected if The displayed version is 1.5.0 or any version lower than 1.5.1
  3. Verify version against vulnerable range
    Compare the installed version number to the affected range: any version below 1.5.1 is vulnerable
    Affected if The version shown is less than 1.5.1 (for example: 1.5.0, 1.4.x, 1.3.x, etc.)
  4. Inspect application package (APK) if available
    If the APK file is available on the device or in a deployment package, examine the APK's manifest or metadata for the versionName attribute using standard APK inspection tools
    Affected if The APK versionName attribute reflects a version lower than 1.5.1

The environment is affected if the Aremis 4 Nomad Android application is installed with any version lower than 1.5.1.

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 dynamic SQL queries with parameterized queries or prepared statements in all database interactions, implement strict input validation and sanitization on the client and server side, and apply principle of least privilege to database accounts. Update to the latest patched version of the application when available.

Recommended fix High confidence

1.5.1 or later

  1. Identify the current version of Aremis 4 Nomads (A4N) Android application installed on devices
  2. Obtain the fixed version 1.5.1 or later from the official vendor distribution channel (Google Play Store, vendor website, or enterprise MDM)
  3. Backup any local data if required by vendor documentation
  4. Upgrade the A4N application to version 1.5.1 or latest available version on all affected Android devices
  5. Verify the upgrade was successful by checking the application version
  6. Test that the application functions normally after upgrade

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

Fix this in Aremis 4 Nomads Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34909 — 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-34909 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