LiveActive security incident?Get immediate response
CVE Record

CVE-2025-60876: BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-tar...

BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/query), allowing the request line to be split and attacker-controlled headers to be injected. To preserve the HTTP/1.1 request-line shape METHOD SP request-target SP HTTP/1.1, a raw space (0x20) in the request-target must also be rejected (clients should use %20).

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

BusyBox wget could mishandle unsafe characters in a URL path or query, letting a crafted request alter the HTTP request it sends. This matters most where embedded systems, appliances, scripts, or automation fetch attacker-influenced URLs. The record is medium severity and does not show active exploitation.

Executive priority

Prioritize inventory and vendor checks for internet-connected or automation-heavy environments using BusyBox. This is not currently evidenced as actively exploited, but the network attack surface and embedded footprint justify timely validation.

Technical view

BusyBox wget through 1.3.7 accepted raw CR, LF, other C0 control bytes, and raw spaces in the HTTP request-target. That could split the request line and inject attacker-controlled headers. CVSS is 6.5, network exploitable, low confidentiality and integrity impact, no privileges or user interaction required.

Likely exposure

Exposure is likely in systems that ship or use BusyBox wget and allow untrusted input to influence fetched URL paths or queries. The source record lists no vendor, product, CPE, or complete affected-product inventory, so asset validation is necessary.

Exploitation context

The bundle does not cite CISA KEV listing or confirmed exploitation in the wild. Public references include technical discussion and an external advisory, so defenders should treat exploitation as plausible but not confirmed by these sources.

Researcher notes

The CVE metadata is sparse: affected vendor/product/CPE fields are n/a. Treat the version statement and request-target parsing behavior as the main grounded facts. Do not assume Siemens product exposure beyond the cited advisory without checking that advisory and product inventory.

Mitigation direction

  • Inventory systems, firmware, containers, and scripts using BusyBox wget.
  • Check BusyBox and device-vendor guidance for fixed versions or vendor-approved updates.
  • Avoid passing user-controlled URLs directly to BusyBox wget.
  • Reject raw control bytes and raw spaces in URL paths and queries before fetches.
  • Use percent-encoding for spaces where URL input is legitimate.

Validation and detection

  • Identify BusyBox wget versions present in deployed assets and SBOMs.
  • Review automation that builds wget URLs from external or low-trust input.
  • Confirm whether vendors list your products as affected or remediated.
  • Test URL validation logic for rejection of raw control characters.
  • Monitor unusual outbound HTTP headers from embedded or appliance environments.
Prepared
Confidence
medium
Sources
6

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 · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-2025-60876 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
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2025-60876Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
siemens-SADPADP container
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-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.