CVE-2024-1735
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability has been identified in armeria-saml versions less than 1.27.2, allowing the use of malicious SAML messages to bypass authentication. All users who rely on armeria-saml older than version 1.27.2 must upgrade to 1.27.2 or later.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA vulnerability in armeria-saml versions before 1.27.2 allows malicious SAML messages to bypass authentication mechanisms. The specific nature of the bypass is not detailed, but the vulnerability is exploitable through crafted SAML authentication requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.27.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify armeria-saml dependencyInspect project build files (pom.xml, build.gradle, requirements.txt) or application classpath for 'armeria-saml' or 'com.linecorp.armeria:armeria-saml' dependencyAffected if The armeria-saml library is present in the project dependencies
-
Determine installed version of armeria-samlRun 'mvn dependency:tree | grep armeria-saml' for Maven projects, or 'gradle dependencies | grep armeria-saml' for Gradle projects, to list the exact version in useAffected if The version shown is below 1.27.2 (e.g., 1.27.1, 1.27.0, 1.26.x, etc.)
-
Check if SAML authentication is configuredReview application configuration files and Armeria server setup code for SAML-related beans or builders (e.g., SamlServiceProvider, saml() method calls in ServerBuilder, SAML-related configuration properties)Affected if SAML authentication is actively configured and enabled in the Armeria server
-
Verify SAML endpoint is exposedInspect network listeners or port configurations to confirm the application exposes endpoints that handle SAML authentication (typically /saml/* paths or custom SAML endpoints)Affected if The server exposes SAML authentication endpoints to clients
The environment is affected if armeria-saml version is below 1.27.2 AND SAML authentication is configured and exposed in the Armeria server
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.27.2
Upgrade armeria-saml to version 1.27.2 or later and verify SAML authentication functionality continues to work correctly.
1.27.2
- Identify your build system (Maven or Gradle) used in your project
- For Maven: Update the armeria-saml dependency version in your pom.xml file to 1.27.2 or later
- For Gradle: Update the armeria-saml dependency version in your build.gradle file to 1.27.2 or later
- Run your build tool to resolve the new dependency (mvn clean install or gradle build)
- Verify the upgrade by running your test suite to ensure the authentication bypass is resolved
- Deploy the updated application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1735 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-1735 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data