CVE-2016-8639
CVE-2016-8639 Vulnerability Analysis & Exploit Intelligence
It was found that foreman before 1.13.0 is vulnerable to a stored XSS via an organization or location name. This could allow an attacker with privileges to set the organization or location name to display arbitrary HTML including scripting code within the web interface.
Published Updated Sources: cvelistV5, redhat
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
1%
chance of exploitation in 30 days
CVSS base
6.1
MEDIUM
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 6.1 | CVSS 3.0 | MEDIUM | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-79
References
5 on the record
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-8639
x_refsource_CONFIRM
- access.redhat.com/errata/RHSA-2018:0336
vendor-advisory, x_refsource_REDHAT
- github.com/theforeman/foreman/pull/3523
x_refsource_CONFIRM
- www.securityfocus.com/bid/94263
vdb-entry, x_refsource_BID
- projects.theforeman.org/issues/15037
x_refsource_CONFIRM
Elsewhere on this site
- the foreman projectevery CVE for this vendor
- CWE-79other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.