CVE-2024-57154
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 · uneditedIncorrect access control in dts-shop v0.0.1-SNAPSHOT allows attackers to bypass authentication via sending a crafted payload to /admin/auth/index.
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 confidencedts-shop v0.0.1-SNAPSHOT has an incorrect access control vulnerability allowing unauthenticated attackers to bypass authentication by sending a crafted payload to the /admin/auth/index endpoint. This is a critical authentication bypass that grants unauthorized administrative access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 if dts-shop is deployedCheck your deployed applications for the dts-shop application. Look for JAR files, WAR files, or application directories containing 'dts-shop' in the name. Inspect running processes or container images for this application.Affected if The dts-shop application is deployed in your environment
-
Verify the installed versionCheck the application version by inspecting the build artifact (JAR/WAR), pom.xml, or the application's startup logs. Look for version string '0.0.1-SNAPSHOT'.Affected if The deployed version is dts-shop v0.0.1-SNAPSHOT
-
Test /admin/auth/index endpoint accessibilitySend an unauthenticated HTTP request to your dts-shop instance at the /admin/auth/index endpoint. Use a tool like curl: curl -v http://<host>:<port>/admin/auth/index. Observe if the endpoint responds without requiring authentication credentials.Affected if The /admin/auth/index endpoint responds to unauthenticated requests (returns 200 OK or exposes administrative functionality instead of redirecting to login or returning 401/403)
-
Inspect authentication configurationReview the application's security configuration files (e.g., Spring Security config, WebSecurityConfig) to verify whether /admin/auth/index is explicitly excluded from authentication requirements or incorrectly configured as permitAll.Affected if The /admin/auth/index endpoint is configured to permit unauthenticated access or lacks proper security filter mappings
Your environment is affected if dts-shop v0.0.1-SNAPSHOT is deployed and the /admin/auth/index endpoint is accessible without authentication.
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.
From vendor dataImplement proper access control checks on the /admin/auth/index endpoint to verify user authentication and authorization before granting access to administrative functions. Validate all authentication tokens/sessions server-side.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-57154 — 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-57154 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