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

> Attackers can retrieve access-log data via the REST API due to insufficient license file validation in Paxton Net2.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2024
- **Updated:** 19 Nov 2024
- **Also known as:** GHSA-mrh2-c3xg-pf82

## What is CVE-2024-48939?

CVE-2024-48939 is a high-severity missing authorization vulnerability in n/a, published on 11 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insufficient validation performed on the REST API License file in Paxton Net2 before 6.07.14023.5015 (SR4) enables use of the REST API with an invalid License File. Attackers may be able to retrieve access-log data.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

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


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

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

## Is CVE-2024-48939 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48939 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48939 is a high-severity missing authorization vulnerability in n/a, published on 11 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48939 exists.

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-48939/ (Markdown: https://insights.sbomify.com/CVE-2024-48939/index.md)
```

## Sources

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

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