org.openidentityplatform.openam:openam-oauth2

CVE-2024-41667

CVE-2024-41667 is a high-severity code injection vulnerability in org.openidentityplatform.openam:openam-oauth2 (maven), affecting versions <= 15.0.3. It is fixed in 15.0.4.

Key facts
CVSS score
8.8
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
org.openidentityplatform.openam:openam-oauth2
Fixed in
15.0.4
Disclosed
2024

Summary

OpenAM is an open access management solution. In versions 15.0.3 and prior, the getCustomLoginUrlTemplate method in RealmOAuth2ProviderSettings.java is vulnerable to template injection due to its usage of user input. Although the developer intended to implement a custom URL for handling login to override the default PingOne Advanced Identity Cloud login page,they did not restrict the CustomLoginUrlTemplate, allowing it to be set freely. Commit fcb8432aa77d5b2e147624fe954cb150c568e0b8 introduces TemplateClassResolver.SAFER_RESOLVER to disable the resolution of commonly exploited classes in FreeMarker template injection. As of time of publication, this fix is expected to be part of version 15.0.4.

Impact

What is code injection?

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

Severity and exposure

CVE-2024-41667 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (15.0.4). Upgrading removes the vulnerable code path.

Affected versions

maven

  • org.openidentityplatform.openam:openam-oauth2 (<= 15.0.3)

Security releases

  • org.openidentityplatform.openam:openam-oauth2 → 15.0.4 (maven)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's Application Detection and Response identifies whether CVE-2024-41667 is reachable in your applications. Explore runtime application protection for your team.

See if CVE-2024-41667 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2024-41667 in your environment

Remediation advice

Upgrade org.openidentityplatform.openam:openam-oauth2 to 15.0.4 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2024-41667

What is CVE-2024-41667?

CVE-2024-41667 is a high-severity code injection vulnerability in org.openidentityplatform.openam:openam-oauth2 (maven), affecting versions <= 15.0.3. It is fixed in 15.0.4. Untrusted input is evaluated as executable code within the application's runtime environment.

How severe is CVE-2024-41667?

CVE-2024-41667 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.openidentityplatform.openam:openam-oauth2 are affected by CVE-2024-41667?

org.openidentityplatform.openam:openam-oauth2 (maven) versions <= 15.0.3 is affected.

Is there a fix for CVE-2024-41667?

Yes. CVE-2024-41667 is fixed in 15.0.4. Upgrade to this version or later.

Is CVE-2024-41667 exploitable, and should I be worried?

Whether CVE-2024-41667 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2024-41667 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-41667?

Upgrade org.openidentityplatform.openam:openam-oauth2 to 15.0.4 or later.

Stop the waste.
Protect your environment with Kodem.