What is CVE-2024-23679?

CVE-2024-23679 is a critical-severity security vulnerability in com.enonic.xp:lib-auth (maven), affecting versions < 7.7.4. It is fixed in 7.7.4.

How severe is CVE-2024-23679?

CVE-2024-23679 has a CVSS score of 9.8 (Critical). 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 com.enonic.xp:lib-auth are affected by CVE-2024-23679?

com.enonic.xp:lib-auth (maven) versions < 7.7.4 is affected.

Is there a fix for CVE-2024-23679?

Yes. CVE-2024-23679 is fixed in 7.7.4. Upgrade to this version or later.

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

Whether CVE-2024-23679 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.

What actually determines whether CVE-2024-23679 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-23679?

Upgrade com.enonic.xp:lib-auth to 7.7.4 or later.

CVE-2024-23679 in com.enonic.xp:lib-auth

Q: How severe is CVE-2024-23679?

CVE-2024-23679 has a CVSS score of 9.8 (Critical). 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.

Q: Which versions of com.enonic.xp:lib-auth are affected by CVE-2024-23679?

com.enonic.xp:lib-auth (maven) versions < 7.7.4 is affected.

Q: Is there a fix for CVE-2024-23679?

Yes. CVE-2024-23679 is fixed in 7.7.4. Upgrade to this version or later.

Q: Is CVE-2024-23679 exploitable, and should I be worried?

Whether CVE-2024-23679 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.

Q: What actually determines whether CVE-2024-23679 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.

Q: How do I fix CVE-2024-23679?

Upgrade com.enonic.xp:lib-auth to 7.7.4 or later.

Summary

com.enonic.xp:lib-auth vulnerable to Session Fixation

Workarounds

Don't use lib-auth for login.
Java API uses low-level structures and allows to invalidate previous session before auth-info is added.

References

https://github.com/enonic/xp/issues/9253

Impact

All id-providers using lib-auth login method.

CVE-2024-23679 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no 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 (7.7.4); upgrading removes the vulnerable code path.

Affected versions

com.enonic.xp:lib-auth (< 7.7.4)

Security releases

com.enonic.xp:lib-auth → 7.7.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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

https://github.com/enonic/xp/commit/0189975691e9e6407a9fee87006f730e84f734ff
https://github.com/enonic/xp/commit/2abac31cec8679074debc4f1fb69c25930e40842
https://github.com/enonic/xp/commit/1f44674eb9ab3fbab7103e8d08067846e88bace4

Frequently Asked Questions

What is CVE-2024-23679? CVE-2024-23679 is a critical-severity security vulnerability in com.enonic.xp:lib-auth (maven), affecting versions < 7.7.4. It is fixed in 7.7.4.
How severe is CVE-2024-23679? CVE-2024-23679 has a CVSS score of 9.8 (Critical). 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 com.enonic.xp:lib-auth are affected by CVE-2024-23679? com.enonic.xp:lib-auth (maven) versions < 7.7.4 is affected.
Is there a fix for CVE-2024-23679? Yes. CVE-2024-23679 is fixed in 7.7.4. Upgrade to this version or later.
Is CVE-2024-23679 exploitable, and should I be worried? Whether CVE-2024-23679 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-23679 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-23679? Upgrade com.enonic.xp:lib-auth to 7.7.4 or later.