# CVE-2022-34908: Missing authorization in n/a

> Attackers can access application data without authentication by sending simple HTTP requests to unprotected endpoints in the A4N Android application.

- **Severity:** High 8.2 (`CVSS:3.1/AC:L/AV:N/A:N/C:H/I:L/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2023
- **Updated:** 30 May 2025
- **Also known as:** GHSA-34vj-fgrq-mq4v

## What is CVE-2022-34908?

CVE-2022-34908 is a high-severity missing authorization vulnerability in n/a, published on 27 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2022-34908?

It affects 1 product.


Products: Aremis Aremis 4 Nomads.

## How do I fix CVE-2022-34908?

No fix has been published for CVE-2022-34908 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-34908 being exploited?

There is no known exploitation of CVE-2022-34908 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-34909](https://insights.sbomify.com/CVE-2022-34909/): SQL injection in n/a (high 7.7)
- [CVE-2022-34910](https://insights.sbomify.com/CVE-2022-34910/): Information disclosure in n/a (medium 4.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-34908 and fix it if it is affected.

What it is: CVE-2022-34908 is a high-severity missing authorization vulnerability in n/a, published on 27 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-34908 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-34908/ (Markdown: https://insights.sbomify.com/CVE-2022-34908/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-34908
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-34908
- OSV: https://osv.dev/vulnerability/CVE-2022-34908

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-34908/
Summaries are generated and may contain mistakes; the official description above is the record.