LiveActive security incident?Get immediate response
CVE Record

CVE-2013-4251: The scipy.weave component in SciPy before 0.12.1 creates insecure temporary directories.

The scipy.weave component in SciPy before 0.12.1 creates insecure temporary directories.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

SciPy before 0.12.1 used unsafe temporary directories in its scipy.weave component. For most organizations this is a legacy dependency issue, not an internet-facing emergency. Risk is mainly where old scientific Python stacks run on shared systems or process untrusted workloads.

Executive priority

Handle through legacy dependency remediation. Prioritize shared research, analytics, and build systems over standard modern workstations, because evidence points to local temporary-file exposure rather than broad remote compromise.

Technical view

The CVE covers insecure temporary directory creation in scipy.weave before SciPy 0.12.1. The source bundle does not provide CVSS, CWE, exploit details, or impact specifics. Treat it as a local file-system safety issue tied to a deprecated-era SciPy component.

Likely exposure

Exposure is most likely in legacy Python environments using SciPy versions before 0.12.1, especially where scipy.weave is exercised on shared hosts or multi-user compute systems.

Exploitation context

No KEV listing or cited source in the bundle confirms active exploitation. The available description supports insecure temporary directory behavior, but not remote exploitability, public weaponization, or a complete impact chain.

Researcher notes

The bundle identifies the affected component and fixed version boundary but omits CVSS, CWE, and impact detail. Additional vendor advisories may clarify package backports or distribution-specific fixes. Do not assume active exploitation from the provided evidence.

Mitigation direction

  • Upgrade SciPy to 0.12.1 or later where affected versions are present.
  • Prefer vendor-fixed distribution packages where SciPy is OS-managed.
  • Identify and retire dependencies on scipy.weave where feasible.
  • Check Debian, Red Hat, SUSE, and Fedora advisories for package-specific guidance.

Validation and detection

  • Inventory Python environments for SciPy versions before 0.12.1.
  • Search codebases for imports or use of scipy.weave.
  • Confirm OS package versions against vendor advisory status.
  • After remediation, verify SciPy reports version 0.12.1 or later.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-2013-4251 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SciPySciPybefore 0.12.1Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.