Security readout for executives and security teams
Plain-English summary
CVE-2017-9847 is a crash bug in libtorrent 1.1.3. A remote attacker can provide a crafted file that causes an application using the vulnerable decoder to crash. The public bundle does not show code execution, data theft, CVSS scoring, or active exploitation.
Executive priority
Treat as a targeted availability risk, not currently as a confirmed breach-enabling flaw. Prioritize if libtorrent 1.1.3 supports customer-facing, automated, or high-availability services that process untrusted files.
Technical view
The issue is in the bdecode function in bdecode.cpp in libtorrent 1.1.3. The reported impact is a heap-based buffer over-read leading to denial of service through application crash when parsing crafted input.
Likely exposure
Exposure is most likely in applications or services that embed libtorrent 1.1.3 and parse attacker-supplied files. The CVE bundle does not identify specific downstream products, package names, operating systems, or deployment patterns.
Exploitation context
The CVE describes remote denial of service via a crafted file. It is not listed in KEV, and the provided sources do not state active exploitation, public weaponization, required privileges, or user interaction details.
Researcher notes
The source bundle is sparse: no CVSS, CWE, patch version, exploit details, or downstream product list are provided. The strongest public facts are the affected component, version 1.1.3, bdecode location, over-read class, and crash impact.
Mitigation direction
- Inventory applications and services that embed libtorrent.
- Identify any use of libtorrent 1.1.3 specifically.
- Check upstream libtorrent guidance and release notes for fixed versions.
- Reduce processing of untrusted files where practical.
- Prioritize internet-facing or automated file-processing workflows first.
Validation and detection
- Review SBOMs, package manifests, and build artifacts for libtorrent 1.1.3.
- Confirm whether exposed workflows parse attacker-supplied files.
- Check crash telemetry for decoder-related failures in affected applications.
- Verify remediation against vendor or upstream libtorrent guidance.
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-9847 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/arvidn/libtorrent/issues/2099CVE 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.