CVE-2021-28122 json
A request-validation issue was discovered in Open5GS 2.1.3 through 2.2.x before 2.2.1.
published 5y ago modified 4mo ago also EUVD-2021-14823
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.0%
- EPSS 4.0% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
A request-validation issue was discovered in Open5GS 2.1.3 through 2.2.x before 2.2.1. The WebUI component allows an unauthenticated user to use a crafted HTTP API request to create, read, update, or delete entries in the subscriber database. For example, new administrative users can be added. The issue occurs because Express is not set up to require authentication.
Patch / fix
- github.com/open5gs/open5gs#838 pull request
- github.com/open5gs/open5gs/compare/v2.2.0...v2.2.1 advisory
Is CVE-2021-28122 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
3.96% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/open5gs/open5gs/issues/837 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
References
-
github.com
/open5gs/open5gs/pull/838
patch, third-party-advisory
-
github.com
/open5gs/open5gs/compare/v2.2.0...v2.2.1
patch, third-party-advisory
-
github.com
/open5gs/open5gs/issues/837
exploit, third-party-advisory
-
github.com
/open5gs/open5gs/releases
release-notes, third-party-advisory
Sources
- CVE List CVE-2021-28122
- NVD CVE-2021-28122
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.