Security readout for executives and security teams
Plain-English summary
This CVE affects samtools htslib 1.4.0 and earlier. A buffer overflow in CRAM rANS decoding could let a malicious or corrupted CRAM file cause code execution in a process that parses it. The public data does not provide CVSS, affected CPEs, or confirmed exploitation.
Executive priority
Treat this as a targeted high-priority dependency cleanup if your organization processes genomic CRAM data. Urgency rises where untrusted files enter automated pipelines. There is no provided evidence of active exploitation, but potential code execution in a parser is material.
Technical view
The issue is a buffer overflow in htslib's CRAM rANS codec in versions 1.4.0 and earlier. Impact is listed as potential arbitrary code execution. Available sources do not describe prerequisites, vulnerable code paths beyond CRAM rANS decoding, exploit maturity, or specific remediation details.
Likely exposure
Exposure is most likely in bioinformatics pipelines, servers, desktops, or bundled tools using htslib 1.4.0 or earlier to read CRAM files. The source bundle lists affected vendor/product fields as unavailable, so dependency inventory is necessary.
Exploitation context
CISA KEV is false in the provided bundle, and no cited source states active exploitation. The plausible risk is malicious file parsing, but the bundle does not provide exploit details, weaponization status, or attack complexity.
Researcher notes
Evidence is sparse: no CVSS vector, CWE, CPE, exploit status, or detailed advisory is included. Focus validation on htslib versioning and CRAM rANS usage. Avoid assuming all samtools deployments are exploitable without confirming vulnerable library versions and file-processing exposure.
Mitigation direction
- Inventory systems and applications that include samtools htslib.
- Identify any htslib versions 1.4.0 or earlier.
- Check samtools htslib 1.4.1 NEWS and current vendor guidance.
- Upgrade or rebuild affected dependencies using confirmed fixed packages.
- Restrict processing of untrusted CRAM files until remediation is complete.
Validation and detection
- Query package managers and build manifests for htslib versions.
- Confirm CRAM-processing workflows and services using htslib.
- Review application dependency trees for statically bundled htslib.
- Verify remediated hosts no longer report htslib 1.4.0 or earlier.
- Document whether any remaining vulnerable use is isolated from untrusted files.
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.
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-2017-1000206 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/samtools/htslib/blob/1.4.1/NEWSCVE 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.