CVE-2002-2374 sun patchpro: Link Following
sun patchpro: no CVSS score yet. EPSS 1.2% estimated probability of exploitation activity in the next 30 days.
On this page
Unspecified vulnerability in pprosetup in Sun PatchPro 2.0 has unknown impact and attack vectors related to "unsafe use of temporary files."
- EPSS
- 1.2% (unchanged from 1.2% a week ago; 1.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 68th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
- CWEs
- CWE-59 Improper Link Resolution Before File Access (Link Following)
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition) - OWASP Top 10
- A01:2025 Broken Access Control, A06:2025 Insecure Design
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Patch: http://sunsolve.sun.com/search/document.do?assetkey=1-21-113176-01-1&searchclause=113176
- Patch: http://www.securityfocus.com/bid/5540
Ask an AI about this CVE
Show the prompt
Explain CVE-2002-2374 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2002-2374?via=ask-ai-copy and https://cve.bz/cve/CVE-2002-2374?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2002-2374 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| sun:patchpro | 2.0 |
Attack patterns (CAPEC)
- CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
- CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High
- CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
- CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
- CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
- CAPEC-132 Symlink Attack Likelihood: Low · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.