CVE-2013-4280 json
Insecure temporary file vulnerability in RedHat vsdm 4.9.6.
published 7y ago modified 4mo ago also EUVD-2013-4178
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
Insecure temporary file vulnerability in RedHat vsdm 4.9.6.
Is CVE-2013-4280 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-4280 updated cvss 2.1
vdsm: /tmp file vulnerability issues
-
Red Hat Enterprise Virtualization 3 vdsmaffected: no fix available
-
Red Hat Storage 2 vdsmaffected: no fix planned “Will not fix”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-4280 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:P/A:N |
Affected products
- RedHat vdsm
Classification
- Weakness
-
- CWE-668 Exposure of Resource to Wrong Sphere
References
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2013-4280
exploit, issue-tracking, vendor-advisory
-
access.redhat.com
/security/cve/cve-2013-4280
vendor-advisory
-
security-tracker.debian.org
/tracker/CVE-2013-4280
third-party-advisory
Sources
- CVE List CVE-2013-4280
- NVD CVE-2013-4280
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.