CVE-2017-5645
Published: 17 April 2017
In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code.
Priority
Status
Package | Release | Status |
---|---|---|
apache-log4j2 Launchpad, Ubuntu, Debian |
impish |
Not vulnerable
(2.10.0-2)
|
hirsute |
Not vulnerable
(2.10.0-2)
|
|
jammy |
Not vulnerable
(2.10.0-2)
|
|
kinetic |
Not vulnerable
(2.10.0-2)
|
|
lunar |
Not vulnerable
(2.10.0-2)
|
|
artful |
Ignored
(end of life)
|
|
bionic |
Not vulnerable
(2.10.0-2)
|
|
cosmic |
Not vulnerable
(2.10.0-2)
|
|
disco |
Not vulnerable
(2.10.0-2)
|
|
eoan |
Not vulnerable
(2.10.0-2)
|
|
focal |
Not vulnerable
(2.10.0-2)
|
|
groovy |
Not vulnerable
(2.10.0-2)
|
|
precise |
Does not exist
|
|
trusty |
Does not exist
|
|
upstream |
Released
(2.7-2)
|
|
xenial |
Needed
|
|
yakkety |
Ignored
(end of life)
|
|
zesty |
Ignored
(end of life)
|
|
mantic |
Not vulnerable
(2.10.0-2)
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 9.8 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | High |
Integrity impact | High |
Availability impact | High |
Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |