LiveActive security incident?Get immediate response
CVE Record

CVE-2013-4280: Insecure temporary file vulnerability in RedHat vsdm 4.9.6.

Insecure temporary file vulnerability in RedHat vsdm 4.9.6.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2013-4280 is an insecure temporary file issue reported in Red Hat vdsm/vsdm. The bundle gives no severity, CVSS score, impact detail, or exploitation evidence. Business urgency depends on whether any legacy Red Hat virtualization hosts still run the affected 2013-era software.

Executive priority

Treat this as a targeted legacy-asset verification item, not a broad emergency, unless affected Red Hat virtualization hosts are still in production.

Technical view

The source bundle describes an insecure temporary file vulnerability in Red Hat vdsm, affecting versions through 2013-07-24. No CWE, CVSS vector, attack prerequisites, impact boundaries, or fixed version are included. The product naming appears inconsistent between “vsdm” and “vdsm.”

Likely exposure

Exposure is most likely limited to legacy environments running Red Hat vdsm/vsdm around version 4.9.6 or versions through 2013-07-24. Modern systems without this component are unlikely to be affected based on the provided bundle.

Exploitation context

The bundle does not identify known exploitation, public exploit availability, or CISA KEV listing. It also does not provide enough technical detail to determine whether exploitation is local, remote, authenticated, or configuration-dependent.

Researcher notes

Evidence is sparse. The CVE text only states an insecure temporary file vulnerability and affected Red Hat vdsm versions through 2013-07-24. Avoid assuming impact, exploitability, or fixed versions without vendor advisory detail.

Mitigation direction

  • Inventory hosts for Red Hat vdsm/vsdm installations and versions.
  • Check Red Hat and distribution advisories for fixed package guidance.
  • Upgrade or remove affected legacy software when vendor guidance confirms remediation.
  • Limit administrative access to affected hosts until exposure is resolved.

Validation and detection

  • Confirm whether vdsm/vsdm is installed on virtualization hosts.
  • Record installed package versions and compare against “through 2013-07-24.”
  • Review Red Hat and Debian tracker entries for remediation status.
  • Document systems where the component is absent or already updated.
Prepared
Confidence
medium
Sources
5

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-4280 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
4Source 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
RedHatvdsmthrough 2013-07-24Listed
Weakness

CWE details

No CWE listed

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