LiveActive security incident?Get immediate response
CVE Record

CVE-2017-11692: The function "Token& Scanner::peek" in scanner.cpp in yaml-cpp 0.5.3 and earlier allows remote attackers to...

The function "Token& Scanner::peek" in scanner.cpp in yaml-cpp 0.5.3 and earlier allows remote attackers to cause a denial of service (assertion failure and application exit) via a '!2' string.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-11692 is a denial-of-service flaw in yaml-cpp. Applications using yaml-cpp 0.5.3 or earlier may crash when they parse a specially crafted YAML string. Business impact depends on whether untrusted users can submit YAML to a service or workflow.

Executive priority

Treat this as a targeted availability risk. It is not described as remote code execution, but affected internet-facing or automation-critical YAML parsers could be forced to exit, interrupting service or pipeline reliability.

Technical view

The issue is in Token& Scanner::peek in scanner.cpp. The CVE states yaml-cpp 0.5.3 and earlier can hit an assertion failure and exit when processing crafted YAML input, producing denial of service rather than data theft or code execution.

Likely exposure

Exposure is most likely in services, tools, CI pipelines, or configuration import features that parse attacker-controlled YAML using yaml-cpp 0.5.3 or earlier. Systems that only parse trusted local YAML have lower practical exposure.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The CVE description identifies a simple crafted input condition, so validation should focus on dependency presence and untrusted YAML parsing paths, not internet exposure alone.

Researcher notes

The source bundle has limited detail: no CVSS vector, CWE, patch commit, or affected CPEs are provided. The strongest claims are yaml-cpp 0.5.3-and-earlier impact, Scanner::peek involvement, assertion failure, and application exit.

Mitigation direction

  • Inventory applications and packages that depend on yaml-cpp.
  • Identify any yaml-cpp versions at 0.5.3 or earlier.
  • Check upstream yaml-cpp and OS vendor advisories for fixed versions.
  • Prioritize services that parse YAML from users, partners, or automation inputs.
  • Add input isolation or crash containment where immediate upgrade is unavailable.

Validation and detection

  • Review software bills of materials and package manifests for yaml-cpp.
  • Confirm runtime library versions on production hosts and containers.
  • Map application features that accept uploaded or remote YAML.
  • Check crash logs for assertion failures in yaml-cpp scanner code.
  • Verify vendor or distribution patches are applied in deployed builds.
Prepared
Confidence
medium
Sources
4

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-2017-11692 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.