dbcve.org
Debian LinuxOperating system · Debian

CVE-2013-2106

HIGH · 7.5 CVSS v3.1 Published 2019-12-03
Fix available
A fix is available. Upgrade to 4.6.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
webauth before 4.6.1 has authentication credential disclosure

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

webauth versions prior to 4.6.1 contain a vulnerability allowing authentication credential disclosure. The specific mechanism of disclosure is not detailed in available sources, but the high CVSS score (7.5) indicates significant risk to authentication security.

MitigationUpgrade webauth to version 4.6.1 or later to remediate the credential disclosure vulnerability.

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
Debian LinuxOperating system
Affected:= 8.0= 9.0= 10.0
WebauthApplication
Affected:< 4.6.1

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

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

  1. Check installed webauth version
    Run 'webauthd --version' or check the package manager: dpkg -l | grep webauth or rpm -q webauth
    Affected if The version shown is less than 4.6.1 or cannot be determined to be 4.6.1 or later
  2. Identify webauth package on Debian systems
    Check if webauth package is installed: dpkg -l | grep -i webauth or dpkg -s webauth
    Affected if webauth package is installed on Debian 8.0, 9.0, or 10.0 systems (these versions ship vulnerable webauth)
  3. Verify webauth service status
    Check if webauth daemon is running: systemctl status webauthd or ps aux | grep webauth
    Affected if webauthd service is active and the version is below 4.6.1
  4. Inspect webauth configuration files
    Examine /etc/webauth.conf or /etc/webauth/webauth.conf for enabled authentication modules
    Affected if webauth is configured and the installed version is prior to 4.6.1, making credential disclosure possible

A system is affected if webauth version is below 4.6.1 OR if running Debian 8.0/9.0/10.0 with webauth installed, regardless of configuration state.

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
Upgrade available Upgrade to 4.6.1 or later
Fixed in 4.6.1
Interim mitigation

Upgrade webauth to version 4.6.1 or later to remediate the credential disclosure vulnerability.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-2106 — 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-2013-2106 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