dbcve.org
Aremis 4 NomadsApplication · Aremis

CVE-2022-34908

HIGH · 7.5 CVSS v3.1 Published 2023-02-27
Fix available
A fix is available. Upgrade to 1.5.1 or later.
See remediation →
84/100
Remediation priority · High
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 possesses an authentication mechanism; however, some features do not require any token or cookie in a request. Therefore, an attacker may send a simple HTTP request to the right endpoint, and obtain authorization to retrieve application data.

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 Android application 1.5.0 has a broken authentication flaw where certain API endpoints do not enforce the existing authentication mechanism. Despite having an authentication system, some endpoints accept requests without requiring tokens or cookies, allowing unauthenticated attackers to retrieve sensitive application data via simple HTTP requests.

MitigationImplement and enforce proper authentication validation (token/cookie checks) on all API endpoints to ensure every request is authenticated before granting access to data.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 A4N or Aremis 4 Nomads application is present
    Check installed applications on Android devices or MDM console for 'A4N', 'Aremis', or 'Aremis 4 Nomads'
    Affected if The application is installed on any device in the environment
  2. Determine the installed application version
    Access the app version through Android device settings (Apps > A4N/Aremis 4 Nomads > Version) or query via MDM/EMM inventory
    Affected if The installed version is 1.5.0 or lower (any version below 1.5.1)
  3. Verify authentication enforcement on API endpoints
    If you have access to the backend or can intercept traffic, attempt a GET request to application API endpoints without providing auth tokens or cookies
    Affected if API requests succeed without authentication tokens/cookies and return sensitive data
  4. Check for exposed API documentation or endpoints
    Review any publicly accessible API documentation or test endpoints related to the application
    Affected if API endpoints are reachable without requiring authentication credentials

The environment is affected if Aremis 4 Nomads version 1.5.0 or lower is installed, and unauthenticated access to API endpoints is possible.

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

Implement and enforce proper authentication validation (token/cookie checks) on all API endpoints to ensure every request is authenticated before granting access to data.

Recommended fix Moderate confidence

Aremis 4 Nomads version 1.5.1

  1. 1. Verify current Aremis 4 Nomads application version by checking the app settings or installed APK details
  2. 2. Obtain the fixed version (1.5.1) from the official vendor source at www.aremis.com or authorized distribution channels
  3. 3. Ensure mobile device has sufficient battery or is connected to power before upgrading
  4. 4. Backup any local application data if the upgrade process supports data preservation
  5. 5. Download and install version 1.5.1 of Aremis 4 Nomads for Android
  6. 6. After installation, verify the new version number in application settings
  7. 7. Test authentication flow and confirm token/cookie handling is enforced on all endpoints

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

Fix this in Aremis 4 Nomads Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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