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

Affected versions of this package are vulnerable to Deserialization of Untrusted Data in the deserialization process of untrusted data in the WebAuthn authentication module. An attacker can execute arbitrary code in the context of the application server by supplying crafted serialized objects to a storage attribute that is attacker-writable and read by the WebAuthn module. This is only exploitable if the storage attribute or userAttribute is configured to be user-writable, which is not the default configuration but can occur through delegated administration, provisioning, write access to the backing directory, legacy REST self-registration, or unsafe reconfiguration.

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