CVE-2013-0220
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 · uneditedThe (1) sss_autofs_cmd_getautomntent and (2) sss_autofs_cmd_getautomntbyname function in responder/autofs/autofssrv_cmd.c and the (3) ssh_cmd_parse_request function in responder/ssh/sshsrv_cmd.c in System Security Services Daemon (SSSD) before 1.9.4 allow remote attackers to cause a denial of service (out-of-bounds read, crash, and restart) via a crafted SSSD packet.
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 · high confidenceThe SSSD daemon before version 1.9.4 contains out-of-bounds read vulnerabilities in three functions: sss_autofs_cmd_getautomntent, sss_autofs_cmd_getautomntbyname (autofs responder), and ssh_cmd_parse_request (SSH responder). Remote attackers can send crafted SSSD packets that trigger the out-of-bounds read, causing the daemon to crash and restart, resulting in denial of service.
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.9.3= 0.2.1= 0.3.0= 0.3.1= 0.3.2= 0.3.3= 0.4.0= 0.4.1= 0.5.0= 0.6.0= 0.6.1= 0.7.0CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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.
-
Check installed SSSD versionRun 'rpm -q sssd' (RHEL/Fedora) or 'dpkg -l sssd' (Debian) to retrieve the installed package version, or use 'sssd --version' if availableAffected if The installed version is 1.9.3 or earlier, or matches any of these specific versions: 0.2.1, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.4.0, 0.4.1, 0.5.0, 0.6.0, 0.6.1, 0.7.0
-
Verify autofs responder is enabledInspect /etc/sssd/sssd.conf and look for 'autofs' in the 'services' list or check for an [autofs] provider sectionAffected if The autofs responder is listed in the services configuration or has an [autofs] section present in sssd.conf, making the daemon vulnerable to the sss_autofs_cmd_getautomntent and sss_autofs_cmd_getautomntbyname flaws
-
Verify SSH responder is enabledInspect /etc/sssd/sssd.conf and look for 'ssh' in the 'services' list or check for an [ssh] provider sectionAffected if The SSH responder is listed in the services configuration or has an [ssh] section present in sssd.conf, making the daemon vulnerable to the ssh_cmd_parse_request flaw
-
Confirm SSSD daemon is runningRun 'systemctl status sssd' or 'ps aux | grep sssd' to verify the SSSD daemon process is activeAffected if The SSSD daemon is actively running, as the vulnerability can only be exploited against an active daemon process
You are affected if SSSD version is 1.9.3 or earlier (or matches the specific affected versions) AND either the autofs or SSH responder is enabled in the configuration AND the daemon is running.
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 dataUpgrade SSSD to version 1.9.4 or later to obtain the patched code with proper bounds checking in the autofs and SSH responder packet parsing routines.
- Consultation2.0 h
- Implementation3.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0220 — 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-2013-0220 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