LiveActive security incident?Get immediate response
CVE Record

CVE-2022-28391: BusyBox through 1.35.0 allows remote attackers to execute arbitrary code if netstat is used to print a DNS...

BusyBox through 1.35.0 allows remote attackers to execute arbitrary code if netstat is used to print a DNS PTR record's value to a VT compatible terminal. Alternatively, the attacker could choose to change the terminal's colors.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

BusyBox netstat can mishandle a malicious DNS PTR record when its value is printed to a VT-compatible terminal. A remote attacker controlling that DNS response could influence what the terminal receives, with reported impact up to arbitrary code execution. The risk depends on vulnerable BusyBox use and an operator or process printing the output.

Executive priority

Prioritize patching where BusyBox is used operationally by administrators or embedded systems. The business risk is high because impact includes code execution, but urgency is moderated by required user interaction and no cited active exploitation.

Technical view

CVE-2022-28391 affects BusyBox through 1.35.0. The issue is tied to unsanitized strings printed by netstat from DNS PTR data to VT-compatible terminals. Public patches reference sanitizing printed strings to printable characters. CVSS 3.1 is 8.8 with network attack vector and required user interaction.

Likely exposure

Exposure is most likely on systems running BusyBox through 1.35.0 where netstat prints reverse DNS names to a compatible terminal. The source bundle does not provide product-specific CPEs or vendor package status beyond Alpine references.

Exploitation context

The CVE record describes remote attack potential, but exploitation requires user interaction. The bundle does not show CISA KEV listing or other evidence of active exploitation. Treat exploit status as unconfirmed from the provided sources.

Researcher notes

Key evidence is the CVE description and Alpine patch references. The affected data is sparse: no CPEs, no upstream advisory in the bundle, and no confirmed exploit activity. Focus research on package versions, patch inclusion, and terminal-output sanitization behavior.

Mitigation direction

  • Inventory systems and images for BusyBox through 1.35.0.
  • Check vendor or distribution guidance for a patched BusyBox package.
  • Apply updates that include printed-string sanitization fixes.
  • Limit use of vulnerable netstat output with untrusted DNS data until patched.

Validation and detection

  • Confirm deployed BusyBox versions and package build provenance.
  • Verify whether operational workflows print netstat DNS output to terminals.
  • Check vendor changelogs for the sanitization patches referenced by Alpine.
  • Prioritize validation on administrative hosts, appliances, and recovery images using BusyBox.
Prepared
Confidence
medium
Sources
5

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-88: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. 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
description · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2022-28391 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

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
4Source 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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2022-28391Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
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-88 · source CWE mapping

Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')

Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.