CVE-2010-4226 json
cpio, as used in build 2007.05.10, 2010.07.28, and possibly other versions, allows remote attackers to overwrite arbitrary files via a syml…
published 12y ago modified 4mo ago also EUVD-2010-4200
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
cpio, as used in build 2007.05.10, 2010.07.28, and possibly other versions, allows remote attackers to overwrite arbitrary files via a symlink within an RPM package archive.
Patch / fix
- osc SLE Software Development Kit 12 SP3, SLE Software Development Kit 12 SP2 0.162.0-15.3.1
- build SLE Software Development Kit 12 SP3, SLE Software Development Kit 12 SP2 20171128-9.3.2
- obs-service-source_validator SLE Software Development Kit 12 SP3, SLE Software Development Kit 12 SP2 0.7-9.3.1
suse advisories SUSE-SU-2017:3253-1
Is CVE-2010-4226 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
2.93% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
-
lists.opensuse.org
/opensuse-security-announce/2011-04/msg00000.html
vendor-advisory
-
lists.opensuse.org
/opensuse-updates/2011-03/msg00008.html
vendor-advisory
-
support.novell.com
/security/cve/CVE-2010-4226.html
vendor-advisory
-
bugzilla.novell.com
/show_bug.cgi?id=665768
vendor-advisory
Sources
- CVE List CVE-2010-4226
- NVD CVE-2010-4226
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.