CVE-2013-4120 json
Katello has a Denial of Service vulnerability in API OAuth authentication
published 6y ago modified 4mo ago also EUVD-2013-4048
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
Katello has a Denial of Service vulnerability in API OAuth authentication
Is CVE-2013-4120 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-4120 updated cvss 5.0
katello: DoS in API OAuth authentication
-
Red Hat CloudForms Management Engine 5 katelloaffected: no fix available
-
Red Hat Satellite 6 katello, katello-common, katello-capsule, katello-service, foreman-proxy-contentaffected: no fix planned “Will not fix”
-
Red Hat Subscription Asset Manager katelloaffected: no fix available
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.30% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Affected products
- Katello Katello
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2013-4120
issue-tracking, third-party-advisory
-
access.redhat.com
/security/cve/cve-2013-4120
third-party-advisory
Sources
- CVE List CVE-2013-4120
- NVD CVE-2013-4120
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.