CVE-2019-10185
CVE-2019-10185 Vulnerability Analysis & Exploit Intelligence
It was found that icedtea-web up to and including 1.7.2 and 1.8.2 was vulnerable to a zip-slip attack during auto-extraction of a JAR file. An attacker could use this flaw to write files to arbitrary locations. This could also be used to replace the main running application and, possibly, break out of the sandbox.
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
4%
chance of exploitation in 30 days
CVSS base
8.2
HIGH
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 |
|---|---|---|---|---|---|
| 8.2 | CVSS 3.0 | HIGH | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-22
References
8 on the record
- github.com/AdoptOpenJDK/IcedTea-Web/pull/344
x_refsource_CONFIRM
- github.com/AdoptOpenJDK/IcedTea-Web/issues/327
x_refsource_CONFIRM
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10185
x_refsource_CONFIRM
- lists.opensuse.org/opensuse-security-announce/2019-08/msg00045.html
vendor-advisory, x_refsource_SUSE
- lists.debian.org/debian-lts-announce/2019/09/msg00008.html
mailing-list, x_refsource_MLIST
- seclists.org/bugtraq/2019/Oct/5
mailing-list, x_refsource_BUGTRAQ
- packetstormsecurity.com/files/154748/IcedTeaWeb-Validation-Bypass-Directory-Traversal-Code-Execution.html
x_refsource_MISC
- security.gentoo.org/glsa/202107-51
vendor-advisory, x_refsource_GENTOO
Elsewhere on this site
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.