Open Access Management (OpenAM) is an access management solution. Prior to 16.1.2, the pre-authentication /authservice PLL endpoint accepts a CustomCallback XML element whose className value selects an arbitrary Java class for AuthXMLUtils to load and instantiate without verifying that it implements DSAMECallbackInterface. Default configurations expose the endpoint without authentication, allowing attacker-controlled class initialization and unsafe deserialization of a serialized Subject value to execute code in the server process. Enabling sunRemoteAuthSecurityEnabled does not prevent the vulnerable parsing and instantiation because its check occurs later. This issue is fixed in version 16.1.2.

Affected: Maven: org.openidentityplatform.openam:openam-core

## Summary A pre-authentication remote code execution vulnerability affects OpenAM. The remote authentication endpoint (`/authservice`, PLL) accepts an XML element that names an arbitrary Java class, which the server then loads and instantiates without validation. On a default configuration this is reachable **without authentication** and allows an attacker to run code on the server.

## Impact Unauthenticated remote code execution / full server compromise on any OpenAM instance with default settings.

## Affected All releases up to and including 16.1.1 (the defect predates the Open Identity Platform fork).

## Remediation Upgrade to `16.1.2`. The fix resolves the class named in a `<CustomCallback>` element without running its static initialisers and rejects it unless it implements `DSAMECallbackInterface`, and it constrains deserialisation of the serialised `Subject` value to a class allowlist.

## Interim mitigation If you cannot upgrade immediately:

- **Restrict or block external network access to `/authservice`.** This is the only reliable mitigation. - Optionally, **block PLL requests carrying a `<CustomCallback className="...">` element** at the reverse proxy or WAF. That element is only produced for custom `DSAMECallbackInterface` callbacks, so most deployments never send it — confirm against your own traffic before enforcing. - **Enabling `sunRemoteAuthSecurityEnabled` does *not* mitigate this issue.** The remote-auth security token is checked in `AuthXMLH…

Affected: Ubuntu:16.04:LTS: openam

Open Access Management (OpenAM) is an access management solution. Prior to 16.1.2, the pre-authentication /authservice PLL endpoint accepts a CustomCallback XML element whose className value selects an arbitrary Java class for AuthXMLUtils to load and instantiate without verifying that it implements DSAMECallbackInterface. Default configurations expose the endpoint without authentication, allowing attacker-controlled class initialization and unsafe deserialization of a serialized Subject value to execute code in the server process. Enabling sunRemoteAuthSecurityEnabled does not prevent the vulnerable parsing and instantiation because its check occurs later. This issue is fixed in version 16.1.2.