CVE-2014-0183 json
Versions of Katello as shipped with Red Hat Subscription Asset Manager 1.4 are vulnerable to a XSS via HTML in the systems name when regist…
published 2020-01-02 6 y ago modified 2026-06-17 4 mo ago also EUVD-2014-0235
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
Versions of Katello as shipped with Red Hat Subscription Asset Manager 1.4 are vulnerable to a XSS via HTML in the systems name when registering.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2014-0183 updated cvss 4.3
XSS: HTML in systems name (when registering) gets interpreted on system information page
-
Red Hat Subscription Asset Manager katelloaffected: no fix available
-
Red Hat Satellite 6 katello, katello-common, katello-capsule, katello-service, foreman-proxy-contentnot affected: vulnerable code not present
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
0.66% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Affected products
- Katello Katello
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2014-0183
issue-tracking, vendor-advisory
-
access.redhat.com
/security/cve/cve-2014-0183
vendor-advisory
Sources
- CVE List CVE-2014-0183
- NVD CVE-2014-0183
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.