# CVE-2024-38447: Missing authorization in n/a

> Attackers can access private draft reports belonging to other users by modifying the ID field in requests.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-mq58-p8pv-xx7f

## What is CVE-2024-38447?

CVE-2024-38447 is a high-severity missing authorization vulnerability in n/a, published on 17 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NATO NCI ANET 3.4.1 allows Insecure Direct Object Reference via a modified ID field in a request for a private draft report (that belongs to an arbitrary user).

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2024-38447?

It affects 1 product.


Products: Ncia Advisor Network.

## How do I fix CVE-2024-38447?

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

## Is CVE-2024-38447 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-38446](https://insights.sbomify.com/CVE-2024-38446/): Business logic in n/a (medium 6.5)
- [CVE-2023-31441](https://insights.sbomify.com/CVE-2023-31441/): Null dereference in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-38447 and fix it if it is affected.

What it is: CVE-2024-38447 is a high-severity missing authorization vulnerability in n/a, published on 17 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38447 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-2024-38447/ (Markdown: https://insights.sbomify.com/CVE-2024-38447/index.md)
```

## Sources

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

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