Log4j up to 1.2.17 Deserialization SocketServer deserialization

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.0$0-$5k0.00

Summaryinfo

A vulnerability was found in Log4j. It has been classified as critical. This vulnerability affects the function SocketServer of the component Deserialization. Performing a manipulation results in deserialization. This vulnerability is cataloged as CVE-2019-17571. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Log4j. It has been classified as critical. This affects the function SocketServer of the component Deserialization. The manipulation with an unknown input leads to a deserialization vulnerability. CWE is classifying the issue as CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.

The weakness was shared 12/20/2019 (Website). It is possible to read the advisory at lists.apache.org. This vulnerability is uniquely identified as CVE-2019-17571 since 10/14/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2022-0770). The entry VDB-153476 is related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

  • IBM DB2
  • Red Hat Enterprise Linux
  • IBM SPSS
  • EMC Avamar
  • Hitachi Ops Center

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.0
VulDB Meta Temp Score: 9.0

VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.8
NVD Vector: 🔍

ADP CISA Base Score: 9.8
ADP CISA Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Deserialization
CWE: CWE-502 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

10/14/2019 🔍
12/20/2019 +67 days 🔍
12/21/2019 +1 days 🔍
05/29/2026 +2351 days 🔍

Sourcesinfo

Advisory: USN-4495-1
Status: Not defined

CVE: CVE-2019-17571 (🔍)
GCVE (CVE): GCVE-0-2019-17571
GCVE (VulDB): GCVE-100-147579
CERT Bund: WID-SEC-2022-0770 - IBM DB2: Mehrere Schwachstellen

See also: 🔍

Entryinfo

Created: 12/21/2019 18:11
Updated: 05/29/2026 07:02
Changes: 12/21/2019 18:11 (38), 12/21/2019 18:16 (17), 03/16/2024 09:56 (3), 01/12/2026 02:04 (21), 05/29/2026 07:02 (12)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!