NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Maven

GHSA-hx5q-v6pj-533r: SAML authentication bypass due to missing validation on unsigned SAML messages

criticalCVSS 3.1 9.1

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.

Published Feb 26, 2024 · Updated Mar 15, 2026

Affected packages

com.linecorp.centraldogma:centraldogma-server-auth-saml

Ecosystem
Maven
Affected
<= 0.64.2
Fixed in
0.64.3
Check
mvn dependency:tree -Dincludes=com.linecorp.centraldogma:centraldogma-server-auth-saml

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Patches

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.

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()`

Credited to lishiki.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology