dbcve.org
Cleartext TransmissionWeakness · CWE-319

CVE-2025-6180

HIGH · 8.5 CVSS v4.0 Published 2025-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
No privileges

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 · unedited
The StrongDM Client insufficiently protected a pre-authentication token. Attackers could exploit this to intercept and reuse the token, potentially redeeming valid authentication credentials through a race condition.

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 confidence

The StrongDM Client insufficiently protected a pre-authentication token, allowing attackers to intercept and reuse it. The vulnerability enables redemption of valid authentication credentials through a race condition, representing a token theft and reuse attack vector in the authentication flow.

MitigationApply vendor-provided patches when available; implement additional encryption for token storage and transmission; add token invalidation after use to prevent reuse; review authentication flow for race condition mitigation.

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
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify StrongDM Client installation
    Check for StrongDM Client binaries or service on the system. On Windows, look for C:\Program Files\StrongDM\sdm.exe or similar. On Linux/macOS, check /usr/local/bin/sdm, /opt/sdm/bin/sdm, or via command: which sdm
    Affected if StrongDM Client is installed and running on the system
  2. Determine installed StrongDM Client version
    Run 'sdm --version' or 'sdm version' from the command line, or right-click the sdm.exe file and view Properties > Details for version information
    Affected if Version matches the range specified in StrongDM's security advisory for this CVE (compare your version against vendor-published affected versions)
  3. Inspect pre-authentication token configuration
    Review StrongDM client configuration files in the installation directory or user config directory (e.g., ~/.sdm/ or %APPDATA%\StrongDM\) for settings related to token storage, encryption, or pre-authentication handling
    Affected if Token storage is unencrypted or uses weak protection methods that allow interception
  4. Examine authentication flow for race condition exposure
    Monitor or review logs during authentication attempts for timing windows where tokens could be intercepted. Check if network traffic between client and gateway uses encryption during the pre-authentication phase
    Affected if Pre-authentication token transmission occurs over unencrypted channels or allows sufficient time window for interception
  5. Review authentication logs for reuse indicators
    Check StrongDM client logs (typically in logs/ subdirectory of installation or user config) for duplicate token redemption attempts or unusual authentication patterns
    Affected if Logs show token reuse attempts or authentication anomalies indicating the vulnerability may have been exploited

If StrongDM Client is installed with a version that falls within the affected range per vendor advisories AND the pre-authentication token mechanism is active, the environment is potentially affected by this token theft and reuse vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches when available; implement additional encryption for token storage and transmission; add token invalidation after use to prevent reuse; review authentication flow for race condition mitigation.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6180 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6180 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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