LiveActive security incident?Get immediate response
CVE Record

CVE-2010-0014: System Security Services Daemon (SSSD) before 1.0.1, when the krb5 auth_provider is configured but the KDC...

System Security Services Daemon (SSSD) before 1.0.1, when the krb5 auth_provider is configured but the KDC is unreachable, allows physically proximate attackers to authenticate, via an arbitrary password, to the screen-locking program on a workstation that has any user's Kerberos ticket-granting ticket (TGT); and might allow remote attackers to bypass intended access restrictions via vectors involving an arbitrary password in conjunction with a valid TGT.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This older SSSD flaw can let authentication succeed with any password in a specific Kerberos failure state. The clearest risk is a local attacker unlocking a workstation when Kerberos is configured, the KDC is unreachable, and a user TGT exists. Remote impact is described as possible but not detailed in the provided sources. Exposure is likely limited to legacy Linux environments running SSSD before 1.0.1 with Kerberos authentication configured. Highest concern is workstations using screen locking and Kerberos tickets. Modern systems are likely unaffected if SSSD has been updated, but old images and unmanaged endpoints should be checked. Prioritize this for legacy identity infrastructure and workstation fleets. It is not currently evidenced as broadly exploited, but successful abuse could bypass user authentication. If SSSD before 1.0.1 is present with Kerberos, treat remediation as urgent; otherwise track as legacy exposure cleanup. Mitigation focus: Upgrade SSSD to 1.0.1 or later where vendor-supported packages exist.; Check vendor advisories for distribution-specific fixed package versions.; Review Kerberos authentication fallback behavior on legacy workstations..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2010-0014 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.