LiveActive security incident?Get immediate response
CVE Record

CVE-2017-15874: archival/libarchive/decompress_unlzma.c in BusyBox 1.27.2 has an Integer Underflow that leads to a read acc...

archival/libarchive/decompress_unlzma.c in BusyBox 1.27.2 has an Integer Underflow that leads to a read access violation.

MediumCVSS 5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-15874 is a BusyBox 1.27.2 flaw in LZMA decompression. A local, low-privileged user could trigger an integer underflow that causes invalid read behavior when a crafted archive is processed. Business urgency is moderate because exploitation requires local access and user interaction, and the supplied sources do not show active exploitation.

Executive priority

Treat this as a moderate-priority remediation item for embedded and appliance-heavy environments. It is not supported as actively exploited by the supplied sources, but BusyBox is widely embedded and version visibility is often poor. Focus on inventory and vendor-supported updates.

Technical view

The issue is CWE-191 in archival/libarchive/decompress_unlzma.c. The CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N with score 5.0. Public affected metadata is incomplete, but the title identifies BusyBox 1.27.2. Sources do not name a fix or vendor mitigation.

Likely exposure

Exposure is most likely in Linux systems, embedded firmware, appliances, or containers that include BusyBox 1.27.2 and process LZMA archives through BusyBox. The source bundle does not provide CPEs or a complete affected-version range.

Exploitation context

The CVSS vector indicates local access, low attack complexity, low privileges, and required user interaction. The provided sources do not report active exploitation, and KEV status is false. Avoid assuming remote exposure unless local deployment workflows make BusyBox process untrusted archives.

Researcher notes

Evidence is sparse. The bundle identifies BusyBox 1.27.2 and CWE-191, but affected CPEs, exploit maturity, and fix details are not provided. The CVSS confidentiality impact is high, while integrity and availability are none; validate this against vendor details before escalating risk.

Mitigation direction

  • Inventory BusyBox versions across hosts, firmware, containers, and appliance SBOMs.
  • Check BusyBox or device-vendor guidance for fixed builds or backported patches.
  • Update affected BusyBox packages or firmware when vendor-approved fixes are available.
  • Limit processing of untrusted LZMA archives on systems using affected BusyBox builds.
  • Prioritize vendor-maintained firmware over manual BusyBox replacement on appliances.

Validation and detection

  • Confirm whether BusyBox 1.27.2 is present in target images or firmware.
  • Verify whether BusyBox unlzma code is reachable in operational workflows.
  • Review vendor advisories for affected-version ranges and fixed release details.
  • Check vulnerability management results against actual embedded BusyBox versions.
  • Document systems where affected metadata is uncertain or vendor guidance is absent.
Prepared
Confidence
medium
Sources
3

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.

cwe · low confidence lookup

CWE-191: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-15874 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
Medium
CVSS
5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N1.33.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5Medium
CVSS 3.1 vector shape for CVE-2017-15874Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-191 · source CWE mapping

Integer Underflow (Wrap or Wraparound)

Integer Underflow (Wrap or Wraparound) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.