LiveActive security incident?Get immediate response
CVE Record

CVE-2013-1630: pyshop before 0.7.1 uses HTTP to retrieve packages from the PyPI repository, and does not perform integrity...

pyshop before 0.7.1 uses HTTP to retrieve packages from the PyPI repository, and does not perform integrity checks on package contents, which allows man-in-the-middle attackers to execute arbitrary code via a crafted response to a download operation.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2013-1630 affects pyshop before 0.7.1. It could fetch Python packages over plain HTTP without verifying package integrity, allowing a network attacker to substitute malicious content. Business urgency depends on whether legacy pyshop is still used in build or package distribution workflows. Exposure is most likely in legacy environments still running pyshop before 0.7.1 as a Python package index, cache, or mirror component. Evidence in the bundle does not identify CPEs, vendors, or downstream products. Prioritize remediation if pyshop is part of production build, deployment, or internal package distribution. The vulnerability can affect software supply chain trust, but urgency is lower where pyshop is absent or retired. Mitigation focus: Upgrade pyshop to 0.7.1 or later where still deployed.; Check current pyshop vendor guidance before relying on unsupported legacy software.; Require HTTPS for upstream package retrieval wherever configurable..

Prepared

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2013-1630 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
3Source links

CVSS and timeline data

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

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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