CVE-2019-1010023
CVE-2019-1010023 Vulnerability Analysis & Exploit Intelligence
GNU Libc current is affected by: Re-mapping current loaded library with malicious ELF file. The impact is: In worst case attacker may evaluate privileges. The component is: libld. The attack vector is: Attacker sends 2 ELF files to victim and asks to run ldd on it. ldd execute code. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.
Published Updated Sources: cvelistV5, dwf
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
3%
chance of exploitation in 30 days
CVSS base
5.4
MEDIUM
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
PoC
none · proof-of-concept · active
Automatable
No
can an attacker script all four kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component
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 |
|---|---|---|---|---|---|
| 5.4 | CVSS 3.1 | MEDIUM | — | — | cvelistV5 |
References
5 on the record
- sourceware.org/bugzilla/show_bug.cgi?id=22851
x_refsource_MISC
- www.securityfocus.com/bid/109167
vdb-entry, x_refsource_BID
- support.f5.com/csp/article/K11932200?utm_source=f5support&%3Butm_medium=RSS
x_refsource_CONFIRM
- security-tracker.debian.org/tracker/CVE-2019-1010023
vendor-advisory, x_refsource_DEBIAN
- ubuntu.com/security/CVE-2019-1010023
vendor-advisory, x_refsource_UBUNTU
Elsewhere on this site
- gnu libcevery CVE for this vendor
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.