security.snyk.io Open in urlscan Pro
2600:1408:c400:1594::ecd  Public Scan

Form analysis
0 forms found in the DOM

Text Content

Developer Tools
 * Snyk Learn
 * Snyk Advisor
 * Code Checker

About Snyk
 1. Snyk Vulnerability Database
 2. Maven
 3. org.apache.logging.log4j:log4j-core




DESERIALIZATION OF UNTRUSTED DATA AFFECTING ORG.APACHE.LOGGING.LOG4J:LOG4J-CORE
PACKAGE, VERSIONS [,2.8.2)

--------------------------------------------------------------------------------

SEVERITY

Recommended
9.8
critical
0
10

CVSS ASSESSMENT MADE BY SNYK'S SECURITY TEAM

Learn more


THREAT INTELLIGENCE


Exploit Maturity
Mature
EPSS
87.38% (99th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components
are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Deserialization of Untrusted Data vulnerabilities in an interactive
lesson.

Start learning
 * Snyk ID SNYK-JAVA-ORGAPACHELOGGINGLOG4J-31409
 * published 20 May 2017
 * disclosed 1 Apr 2017
 * credit Marcio Almeida de Macedo

Report a new vulnerability Found a mistake?

INTRODUCED: 1 APR 2017

CVE-2017-5645 Open this link in a new tab

CWE-502 Open this link in a new tab

Share



HOW TO FIX?

Upgrade org.apache.logging.log4j:log4j-core to version 2.8.2 or higher.


OVERVIEW

org.apache.logging.log4j:log4j-core is a logging library for Java.

Affected versions of this package are vulnerable to Deserialization of Untrusted
Data. 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.


DETAILS

Serialization is a process of converting an object into a sequence of bytes
which can be persisted to a disk or database or can be sent through streams. The
reverse process of creating object from sequence of bytes is called
deserialization. Serialization is commonly used for communication (sharing
objects between multiple hosts) and persistence (store the object state in a
file or a database). It is an integral part of popular protocols like Remote
Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System
(JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.

Deserialization of untrusted data (CWE-502), is when the application
deserializes untrusted data without sufficiently verifying that the resulting
data will be valid, letting the attacker to control the state or the flow of the
execution.

Java deserialization issues have been known for years. However, interest in the
issue intensified greatly in 2015, when classes that could be abused to achieve
remote code execution were found in a popular library (Apache Commons
Collection). These classes were used in zero-days affecting IBM WebSphere,
Oracle WebLogic and many other products.

An attacker just needs to identify a piece of software that has both a
vulnerable class on its path, and performs deserialization on untrusted data.
Then all they need to do is send the payload into the deserializer, getting the
command executed.

> Developers put too much trust in Java Object Serialization. Some even
> de-serialize objects pre-authentication. When deserializing an Object in Java
> you typically cast it to an expected type, and therefore Java's strict type
> system will ensure you only get valid object trees. Unfortunately, by the time
> the type checking happens, platform code has already created and executed
> significant logic. So, before the final type is checked a lot of code is
> executed from the readObject() methods of various objects, all of which is out
> of the developer's control. By combining the readObject() methods of various
> classes which are available on the classpath of the vulnerable application, an
> attacker can execute functions (including calling Runtime.exec() to execute
> local OS commands).


REFERENCES

 * Exploit
 * GitHub Commit
 * Jira Issue
 * NVD
 * Nuclei Templates


CVSS SCORES

version 3.1
Expand this section


SNYK

9.8 critical
 * Attack Vector (AV)
   Network
 * Attack Complexity (AC)
   Low
 * Privileges Required (PR)
   None
 * User Interaction (UI)
   None

 * Scope (S)
   Unchanged

 * Confidentiality (C)
   High
 * Integrity (I)
   High
 * Availability (A)
   High

Expand this section


NVD

9.8 critical


PRODUCT

 * Snyk Open Source
 * Snyk Code
 * Snyk Container
 * Snyk Infrastructure as Code
 * Test with Github
 * Test with CLI


RESOURCES

 * Vulnerability DB
 * Documentation
 * Disclosed Vulnerabilities
 * Blog
 * FAQs


COMPANY

 * About
 * Jobs
 * Contact
 * Policies
 * Do Not Sell My Personal Information


CONTACT US

 * Support
 * Report a new vuln
 * Press Kit
 * Events


FIND US ONLINE

 * 
 * 
 * 
 * 


TRACK OUR DEVELOPMENT

 * 
 * 



© 2024 Snyk Limited

Registered in England and Wales. Company number: 09677925

Registered address: Highlands House, Basingstoke Road, Spencers Wood, Reading,
Berkshire, RG7 1NT.