Deserialization of Untrusted Data Affecting org.openidentityplatform.openam:openam-push-notification package, versions [,16.1.1)

Affected versions of this package are vulnerable to Deserialization of Untrusted Data in the SNS callback process. An attacker can trigger class loading and object construction with attacker-controlled data by sending specially crafted SNS callbacks after the in-memory dispatcher entry for a message identifier has expired, leading to potential process execution, file writes, or denial of service depending on the deployment's classpath and environment. This is only exploitable if the Push Notification Service with SNS callbacks is enabled and a low-privileged user can initiate Push Registration and obtain the necessary messageId, shared secret, and challenge.

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, thus allowing the attacker to control the state or the flow of the execution.

• GitHub Advisory
• GitHub Commit