Security readout for executives and security teams
Plain-English summary
yadm 1.10.0 could briefly create files or directories with unsafe permissions during git-related operations. If SSH or PGP keys are handled this way, another local user might gain access. The source bundle does not provide CVSS, confirmed affected package metadata, or patch details.
Executive priority
Treat this as a targeted secret-exposure risk, not a broad internet-facing emergency. Prioritize systems where developers or administrators used yadm 1.10.0 with SSH or PGP keys, because compromised keys can enable follow-on access.
Technical view
CVE-2017-11353 describes a race condition in yadm 1.10.0 tied to git command behavior when permissions are set for new files and directories. The stated impact is potential exposure of SSH and PGP keys. Structured affected vendor/product data is absent in the bundle.
Likely exposure
Exposure is most relevant where yadm 1.10.0 manages dotfiles containing SSH or PGP material, especially on shared Unix-like systems with multiple local users. The bundle does not identify broader affected versions or CPEs.
Exploitation context
No CISA KEV listing or provided source indicates active exploitation. The described issue is a race condition, so practical risk depends on local access, timing, filesystem behavior, and whether sensitive keys were created or managed during the vulnerable window.
Researcher notes
The provided evidence is sparse: no CVSS, CWE, CPE, exploit confirmation, or fix version is included. Analysis should stay anchored to yadm 1.10.0, local race-condition behavior, and potential SSH/PGP key exposure until upstream or distribution guidance is reviewed.
Mitigation direction
- Identify yadm installations and confirm whether version 1.10.0 is present.
- Check upstream yadm issue 74 and Debian bug 868300 for fixed package guidance.
- Avoid managing SSH or PGP private keys through vulnerable yadm workflows.
- Tighten permissions on dotfile repositories, SSH directories, and PGP key material.
- Rotate SSH or PGP keys if exposure cannot be ruled out.
Validation and detection
- Inventory systems and user accounts using yadm-managed dotfiles.
- Review permissions on yadm-created files and directories containing sensitive material.
- Confirm whether SSH or PGP private keys were present in managed paths.
- Check package history against upstream or Debian guidance for fixed versions.
- Prioritize shared systems where untrusted local users had access.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2017-11353 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/TheLocehiliosan/yadm/issues/74CVE reference · x_refsource_CONFIRM
- https://bugs.debian.org/868300CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.