CVE-2013-4251 json
SciPy creates insecure temporary directories
published 7y ago modified 4mo ago also GHSA-xp76-357g-9wqq , PYSEC-2019-156 , EUVD-2019-0129
- cvss
- 7.8
- 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 37%
- public exploits
- 0
- none known
Summary
The scipy.weave component in SciPy before 0.12.1 creates insecure temporary directories.
Patch / fix
- pypi scipy 0.12.1
- scipy scipy 0.12.1
Is CVE-2013-4251 in your dependencies? 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-4251 updated cvss 3.6
scipy: weave /tmp and current directory issues
-
Red Hat Enterprise Linux 6 scipyaffected: no fix planned “Will not fix”
-
Red Hat Enterprise Linux 7 scipynot affected: vulnerable code not present
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.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | scipy | <0.12.1 |
0.12.1 |
Affected products
- SciPy SciPy
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
github.com
/scipy/scipy/commit/bd296e0336420b840fcd2faabb97084fd252a973
web, patch, third-party-advisory
-
security-tracker.debian.org
/tracker/CVE-2013-4251
web, patch, third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2013-4251
web, issue-tracking, third-party-advisory, report
-
bugzilla.suse.com
/show_bug.cgi?id=CVE-2013-4251
web, issue-tracking, third-party-advisory, report
-
access.redhat.com
/security/cve/cve-2013-4251
web, third-party-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2013-November/120696.html
web, mailing-list, third-party-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2013-October/119759.html
web, mailing-list, third-party-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2013-October/119771.html
web, mailing-list, third-party-advisory
-
securityfocus.com
/bid/63008
third-party-advisory, vdb-entry, web
-
exchange.xforce.ibmcloud.com
/vulnerabilities/88052
web, third-party-advisory, vdb-entry
-
nvd.nist.gov
/vuln/detail/CVE-2013-4251
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/scipy/PYSEC-2019-156.yaml
web
-
github.com
/scipy/scipy
package
-
github.com
/advisories/GHSA-xp76-357g-9wqq
advisory
Sources
- CVE List CVE-2013-4251
- GitHub Advisory GHSA-xp76-357g-9wqq
- NVD CVE-2013-4251
- OSV PYSEC-2019-156
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.