CVE-2022-38870 Information disclosure in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2022-38870 and fix it if it is affected.
What it is: CVE-2022-38870 is a high-severity vulnerability in Free5gc Free5gc, published on 25 Oct 2022. 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-2022-38870 exists.
Affected product: Free5gc Free5gc. 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-38870/ (Markdown: https://insights.sbomify.com/CVE-2022-38870/index.md)
Attackers can access sensitive information due to missing authentication in Free5gc, impacting 5G core network security.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2022-38870?
CVE-2022-38870 is a high-severity vulnerability in Free5gc Free5gc, published on 25 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Free5gc v3.2.1 is vulnerable to Information disclosure.
Weakness: CWE-306
Which versions are affected by CVE-2022-38870?
It affects 1 product.
Products include Free5gc Free5gc.
How do I fix CVE-2022-38870?
No fix has been published for CVE-2022-38870 yet. Limit exposure of the affected software until one is available.
Is CVE-2022-38870 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-38870 exists.
Public exploit code: 1 Nuclei template.
Other vulnerabilities in Free5gc Free5gc
- CVE-2026-44327 free5GC: NEF nnef-oam route group is unauthenticated; no-token requests reach the OAM handler
- CVE-2026-44329 free5GC's SMF UPI management interface lacks auth middleware; unauthenticated topology read/write requests reach handlers
- CVE-2026-44330 free5GC's NEF nnef-pfdmanagement API is unauthenticated; forged bearer tokens can read PFD data and create/delete PFD subscriptions
- CVE-2025-63679 Memory corruption in n/a
- CVE-2026-44315 free5GC's NEF 3gpp-pfd-management API is unauthenticated; forged bearer tokens can create, read, and delete PFD transactions
Sources
Also known as GHSA-r9r4-j5ch-84qf.