directory traversal for in-place extracts with untrusted v2 and v3 source packages with debian.tar
Noroxi assessment
Priority: Plan (action score 40/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.2% (FIRST EPSS); higher than 88% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Debian dpkg 1.18.26, 1.19.8, 1.20.10.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Add it to your regular patch cycle. Upgrade to Debian dpkg 1.18.26, 1.19.8, 1.20.10 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Dpkg::Source::Archive in dpkg, the Debian package management system, before version 1.21.8, 1.20.10, 1.19.8, 1.18.26 is prone to a directory traversal vulnerability. When extracting untrusted source packages in v2 and v3 source package formats that include a debian.tar, the in-place extraction can lead to directory traversal situations on specially crafted orig.tar and debian.tar tarballs.
- Published
- May 26, 2022
- Updated
- Jun 17, 2026
- EPSS
- 3.2% · 88th percentile
- CWE
- CWE-22
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| debian | dpkg | cpe:2.3:a:debian:dpkg |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| netapp | ontap select deploy administration utility | cpe:2.3:a:netapp:ontap_select_deploy_administration_utility |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- debian debian linux11.0
- debian debian linux9.0
- debian dpkg1.21.0 and later · before 1.21.8
- debian dpkg1.14.17 and later · before 1.18.26
- debian dpkg1.19.0 and later · before 1.19.8
- debian dpkg1.20.0 and later · before 1.20.10
- netapp ontap select deploy administration utilityall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (debian). Independent of NVD's CPE analysis and usually ahead of it.
Debian dpkg
- 1.14.17 and later · before 1.21.8affectedfixed in 1.20.10, 1.19.8, 1.18.26
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.13 | dpkg | from 1.14.17 · before 1.20.10-r0 | 1.20.10-r0 |
| Alpine:v3.16 | dpkg | from 1.14.17 · before 1.21.8-r0 | 1.21.8-r0 |
| Debian:10 | dpkg | before 1.19.8 | 1.19.8 |
| Debian:11 | dpkg | before 1.20.10 | 1.20.10 |
| Debian:12 | dpkg | before 1.21.8 | 1.21.8 |
| Debian:9 | dpkg | before 1.18.26 | 1.18.26 |
| SUSE:Linux Enterprise Micro 5.3 | update-alternatives | before 1.19.0.4-150000.4.4.1 | 1.19.0.4-150000.4.4.1 |
| SUSE:Linux Enterprise Micro 5.3 | update-alternatives | before 1.19.0.4-150000.4.4.1 | 1.19.0.4-150000.4.4.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP3 | dpkg | before 1.19.0.4-150000.4.4.1 | 1.19.0.4-150000.4.4.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP3 | dpkg | before 1.19.0.4-150000.4.4.1 | 1.19.0.4-150000.4.4.1 |
| SUSE:Linux Enterprise Server 12 SP5 | update-alternatives | before 1.18.4-16.3.5 | 1.18.4-16.3.5 |
Same product
debian: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-8283dpkg-source in dpkg 1.3.0 through 1.18.23 is able to use a non-GNU patch program and does not offer a protection mechanism for blank-indente40Plan
- CVE-2025-6297dpkg-deb: Fix cleanup for control member with restricted directories32Monitor
- CVE-2015-0860Off-by-one error in the extracthalf function in dpkg-deb/extract.c in the dpkg-deb component in Debian dpkg 1.16.x before 1.16.17 and 1.17.x31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2014-8625Jan 20, 2015 · Multiple format string vulnerabilities in the parse_error_msg function in parsehelp.c in dpkg before 1.17.22 allow remote attackers to cause28Monitor
- ← EarlierCVE-2015-0840Apr 13, 2015 · The dpkg-source command in Debian dpkg before 1.16.16 and 1.17.x before 1.17.25 allows remote attackers to bypass signature verification via18Monitor
- Later →CVE-2026-2219Mar 7, 2026 · It was discovered that dpkg-deb (a component of dpkg, the Debian package management system) does not properly validate the end of the data s30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Debian dpkg | 1.18.26 | Vendor (CNA) |
| Debian dpkg | 1.19.8 | Vendor (CNA) |
| Debian dpkg | 1.20.10 | Vendor (CNA) |
| alpine:dpkg | 1.20.10-r0 · Alpine:v3.13 | Package registry (OSV) |
| debian:dpkg | 1.21.8 · Debian:12 | Package registry (OSV) |
| opensuse:dpkg | 1.19.0.4-150000.4.4.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:update-alternatives | 1.19.0.4-150000.4.4.1 · openSUSE:Leap Micro 5.2 | Package registry (OSV) |
| suse:dpkg | 1.19.0.4-150000.4.4.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP3 | Package registry (OSV) |
| suse:update-alternatives | 1.18.4-16.3.5 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:update-alternatives | 1.19.0.4-150000.4.4.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-22-0388 · May 31, 2022(Ubuntu Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) { return res.sendStatus(400);}res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=1f23dddc17f69c9598477098c7fb9936e15fa495
- git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=58814cacee39c4ce9e2cd0e3a3b9b57ad437eff5
- git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=7a6c03cb34d4a09f35df2f10779cbf1b70a5200b
- git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=faa4c92debe45412bfcf8a44f26e827800bb24be
- lists.debian.org/debian-lts-announce/2022/05/msg00033.html
- lists.debian.org/debian-security-announce/2022/msg00115.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.