CVE-2019-3893
CVE-2019-3893 Vulnerability Analysis & Exploit Intelligence
In Foreman it was discovered that the delete compute resource operation, when executed from the Foreman API, leads to the disclosure of the plaintext password or token for the affected compute resource. A malicious user with the "delete_compute_resource" permission can use this flaw to take control over compute resources managed by foreman. Versions before 1.20.3, 1.21.1, 1.22.0 are vulnerable.
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
2%
chance of exploitation in 30 days
CVSS base
4.9
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 |
|---|---|---|---|---|---|
| 4.9 | CVSS 3.0 | MEDIUM | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-732
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1574.010Hijack Execution Flow: ServicesFile Permissions Weakness
- T1548Abuse Elevation Control Mechanism
- T1083File and Directory Discovery
References
5 on the record
- www.securityfocus.com/bid/107846
vdb-entry, x_refsource_BID
- www.openwall.com/lists/oss-security/2019/04/14/2
mailing-list, x_refsource_MLIST
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3893
x_refsource_CONFIRM
- projects.theforeman.org/issues/26450
x_refsource_MISC
- github.com/theforeman/foreman/pull/6621
x_refsource_MISC
Elsewhere on this site
- the foreman projectevery CVE for this vendor
- CWE-732other 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.