Security readout for executives and security teams
Foreman versions before 1.1 had a flaw in how fact and report imports handled YAML data. A remote attacker could send a crafted YAML object to those import APIs and execute arbitrary code. The business risk is highest where old Foreman systems remain reachable by untrusted networks or users. Exposure is likely limited to organizations still running Foreman before 1.1, especially where fact or report import APIs are network-reachable. The bundle does not identify affected CPEs, packages, hosted services, or downstream distributions. Prioritize remediation if Foreman before 1.1 exists in production or management networks. Arbitrary code execution against infrastructure management tooling can affect many dependent systems. If no such legacy Foreman deployment exists, track as historical risk only. Mitigation focus: Identify any Foreman instances older than version 1.1.; Confirm vendor guidance from Foreman's issue and security pages.; Upgrade affected Foreman deployments to a supported fixed release..
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.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2013-0171 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
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.