What is GHSA-HX5Q-V6PJ-533R?

GHSA-HX5Q-V6PJ-533R is a critical-severity security vulnerability in com.linecorp.centraldogma:centraldogma-server-auth-saml (maven), affecting versions <= 0.64.2. It is fixed in 0.64.3.

How severe is GHSA-HX5Q-V6PJ-533R?

GHSA-HX5Q-V6PJ-533R has a CVSS score of 9.1 (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.linecorp.centraldogma:centraldogma-server-auth-saml are affected by GHSA-HX5Q-V6PJ-533R?

com.linecorp.centraldogma:centraldogma-server-auth-saml (maven) versions <= 0.64.2 is affected.

Is there a fix for GHSA-HX5Q-V6PJ-533R?

Yes. GHSA-HX5Q-V6PJ-533R is fixed in 0.64.3. Upgrade to this version or later.

Is GHSA-HX5Q-V6PJ-533R exploitable, and should I be worried?

Whether GHSA-HX5Q-V6PJ-533R 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 GHSA-HX5Q-V6PJ-533R 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.

GHSA-HX5Q-V6PJ-533R

Q: How severe is GHSA-HX5Q-V6PJ-533R?

GHSA-HX5Q-V6PJ-533R has a CVSS score of 9.1 (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: Is there a fix for GHSA-HX5Q-V6PJ-533R?

Yes. GHSA-HX5Q-V6PJ-533R is fixed in 0.64.3. Upgrade to this version or later.

Q: Is GHSA-HX5Q-V6PJ-533R exploitable, and should I be worried?

Whether GHSA-HX5Q-V6PJ-533R 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 GHSA-HX5Q-V6PJ-533R 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 GHSA-HX5Q-V6PJ-533R?

Upgrade com.linecorp.centraldogma:centraldogma-server-auth-saml to 0.64.3 or later.

Summary

SAML authentication bypass due to missing validation on unsigned SAML messages

Workarounds

A user can manually upgrade the armeria-saml module with the one from Armeria 1.27.2 or later, either by replacing the JAR in the Central Dogma distribution or by updating the dependency tree of the build.

References

SamlMessageUtil.validateSignature()

Impact

When SAML is used as the authentication mechanism, Central Dogma accepts unsigned SAML messages (assertions, logout requests, etc.) as they are, rather than rejecting them by default. As a result, an attacker can forge a SAML message to authenticate themselves, despite the fact that such an unsigned SAML message should be rejected.

GHSA-HX5Q-V6PJ-533R has a CVSS score of 9.1 (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 (0.64.3); upgrading removes the vulnerable code path.

Affected versions

com.linecorp.centraldogma:centraldogma-server-auth-saml (<= 0.64.2)

Security releases

com.linecorp.centraldogma:centraldogma-server-auth-saml → 0.64.3 (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

The vulnerability has been patched in Central Dogma 0.64.3 by updating its Armeria dependency to 1.27.2. All users who use SAML as the authentication mechanism must upgrade from 0.64.3 or later.

Frequently Asked Questions

What is GHSA-HX5Q-V6PJ-533R? GHSA-HX5Q-V6PJ-533R is a critical-severity security vulnerability in com.linecorp.centraldogma:centraldogma-server-auth-saml (maven), affecting versions <= 0.64.2. It is fixed in 0.64.3.
How severe is GHSA-HX5Q-V6PJ-533R? GHSA-HX5Q-V6PJ-533R has a CVSS score of 9.1 (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.linecorp.centraldogma:centraldogma-server-auth-saml are affected by GHSA-HX5Q-V6PJ-533R? com.linecorp.centraldogma:centraldogma-server-auth-saml (maven) versions <= 0.64.2 is affected.
Is there a fix for GHSA-HX5Q-V6PJ-533R? Yes. GHSA-HX5Q-V6PJ-533R is fixed in 0.64.3. Upgrade to this version or later.
Is GHSA-HX5Q-V6PJ-533R exploitable, and should I be worried? Whether GHSA-HX5Q-V6PJ-533R 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 GHSA-HX5Q-V6PJ-533R 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 GHSA-HX5Q-V6PJ-533R? Upgrade com.linecorp.centraldogma:centraldogma-server-auth-saml to 0.64.3 or later.