Security readout for executives and security teams
Plain-English summary
Binwalk can be tricked into writing extracted files outside the intended folder when a user analyzes a malicious PFS filesystem with extraction enabled. The source bundle says this can lead to code execution by placing a malicious binwalk plugin. Risk is highest for firmware analysis teams and automated intake pipelines.
Executive priority
Prioritize remediation where binwalk handles untrusted firmware or customer-supplied samples. The issue is not broadly internet-exposed, but it can compromise analyst workstations or build-analysis infrastructure if unsafe extraction workflows exist.
Technical view
CVE-2022-4510 is a CWE-22 path traversal in binwalk's PFS extractor, associated with src/binwalk/plugins/unpfs.py. Affected versions are 2.1.2b through 2.3.3 included. The CVSS 3.1 score is 7.8, with local attack vector and required user interaction through extraction mode.
Likely exposure
Organizations using binwalk to extract firmware or filesystem samples are exposed, especially if analysts or automation run binwalk -e on untrusted submissions. General servers are less likely exposed unless binwalk is installed and used in analysis workflows.
Exploitation context
The bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires a crafted PFS filesystem and a user or process running binwalk extraction mode. Reported impact includes arbitrary file extraction paths and possible code execution through plugin placement.
Researcher notes
Evidence supports a path traversal in the PFS extractor and possible code execution via plugin placement. The source bundle does not provide exploit prevalence or a specific universal fixed version, so validation should rely on local package metadata and vendor advisories.
Mitigation direction
- Update binwalk using trusted vendor or distribution packages where fixes are available.
- Do not run affected binwalk versions on untrusted PFS files with extraction enabled.
- Run firmware extraction in isolated, non-privileged sandboxes.
- Restrict write access to binwalk plugin directories.
- Check ReFirm Labs, Gentoo, and Debian guidance for fixed package status.
Validation and detection
- Inventory binwalk installations and confirm versions are not 2.1.2b through 2.3.3.
- Identify automated pipelines that run binwalk extraction on external samples.
- Review whether extraction jobs run with unnecessary privileges or persistent home directories.
- Audit binwalk plugin directories for unexpected modules.
- Confirm distro advisories are reflected in deployed package versions.
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.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection 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 lookupExecution 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 lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-4510 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
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/ReFirmLabs/binwalk/pull/617CVE reference
- https://security.gentoo.org/glsa/202309-07CVE reference
- https://lists.debian.org/debian-lts-announce/2025/12/msg00022.htmlCVE reference
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.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.