CVE-2012-2599

Exp

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2012-3835. Reason: This issue was MERGED into CVE-2012-3835 in accordance with CVE content decisions, because it is the same type of vulnerability and affects the same versions. Notes: All CVE users should reference CVE-2012-3835 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage

Published: 2020-02-20 Last update: 2023-11-07 Assigner: [email protected] Source: [email protected]

Conclusion & alert: This CVE is rejected; it is not tracked as an active vulnerability. Core evidence: 2 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Do not treat as an active exposure for patching queues—follow the CVE record status and authoritative vendor or program statements only.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2012-2599

EDB-ID Source Kind Published Link
20062 exploit_db edb 2012-07-23 Exploit-DB ↗
18800 exploit_db edb 2012-04-29 Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2012-2599

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2024-02-08 0.24%

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2012-2599

CVSS metrics for this CVE.

No CVSS data in dataset for this CVE.

Weakness enumeration for CVE-2012-2599

Affected software / configurations for CVE-2012-2599

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2012-2599

URL Tags
No references in dataset.
cvelogic Threat Intelligence