org.openidentityplatform.openam:openam-core 16.0.5

Direct Vulnerabilities

Known vulnerabilities in the org.openidentityplatform.openam:openam-core package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Vulnerability	Vulnerable Version
H Improper Authorization Affected versions of this package are vulnerable to Improper Authorization via the `session management endpoint`. An attacker can access session credentials of other users, including those with higher privileges, by making authenticated requests with knowledge of a target user's identity identifier. This is only exploitable if stateful session storage is used and the session management endpoint is exposed. How to fix Improper Authorization? Upgrade `org.openidentityplatform.openam:openam-core` to version 16.1.1 or higher.	[,16.1.1)
H Insertion of Sensitive Information Into Sent Data Affected versions of this package are vulnerable to Insertion of Sensitive Information Into Sent Data via the CDCServlet process. An attacker can gain access to a user's session by inducing a logged-in user to visit a crafted URL, which results in the user's session token being sent to an attacker-controlled endpoint. This is only exploitable if Cross-Domain Single Sign-On (CDSSO) is enabled and a non-default configuration is not present. How to fix Insertion of Sensitive Information Into Sent Data? Upgrade `org.openidentityplatform.openam:openam-core` to version 16.1.1 or higher.	[,16.1.1)
H Server-side Request Forgery (SSRF) Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the `/sessionservice` endpoint when authenticated users register URLs for session event notifications without sufficient restriction. An attacker can cause the server to make outbound requests to arbitrary destinations by supplying attacker-controlled URLs, potentially exposing sensitive session-related data. How to fix Server-side Request Forgery (SSRF)? Upgrade `org.openidentityplatform.openam:openam-core` to version 16.1.1 or higher.	[,16.1.1)
H Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') Affected versions of this package are vulnerable to Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') via the `_queryId` parameter in the CREST REST API endpoints. An attacker can manipulate LDAP queries by injecting arbitrary LDAP metacharacters, potentially enabling user enumeration and blind LDAP injection by sending crafted requests to the affected endpoints. This is only exploitable if the attacker is authenticated with a valid SSO token. How to fix Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')? Upgrade `org.openidentityplatform.openam:openam-core` to version 16.1.1 or higher.	[,16.1.1)
H Authorization Bypass Through User-Controlled Key Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key in the `token-read` process. An attacker can generate unauthorized OAuth2 bearer tokens with arbitrary user, client, realm, and scope values by injecting attacker-controlled JSON into the shared Core Token Store under a known identifier. This is only exploitable if the OAuth2 Provider service is enabled in a realm and the attacker can register a push notification, allowing them to trigger the vulnerable path. How to fix Authorization Bypass Through User-Controlled Key? Upgrade `org.openidentityplatform.openam:openam-core` to version 16.1.1 or higher.	[,16.1.1)

Vulnerability

Vulnerable Version

Improper Authorization

Affected versions of this package are vulnerable to Improper Authorization via the session management endpoint. An attacker can access session credentials of other users, including those with higher privileges, by making authenticated requests with knowledge of a target user's identity identifier. This is only exploitable if stateful session storage is used and the session management endpoint is exposed.

How to fix Improper Authorization?