cve.bz

CVE-2009-0538 symantec pcanywhere

no score yetEPSS 0.4%Fix available

symantec pcanywhere: no CVSS score yet. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Format string vulnerability in Symantec pcAnywhere before 12.5 SP1 allows local users to read and modify arbitrary memory locations, and cause a denial of service (application crash) or possibly have unspecified other impact, via format string specifiers in the pathname of a remote control file (aka .CHF file).
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-134 Use of Externally-Controlled Format String
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2009-0538 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2009-0538?via=ask-ai-copy and https://cve.bz/cve/CVE-2009-0538?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-2009-0538 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.

ProductAffected
symantec:pcanywherethrough 12.5
symantec:pcanywhere10.0
symantec:pcanywhere10.5
symantec:pcanywhere11.0
symantec:pcanywhere11.0.1
symantec:pcanywhere11.5
symantec:pcanywhere11.5.1
symantec:pcanywhere12.0
symantec:pcanywhere12.1

Attack patterns (CAPEC)

  • CAPEC-67 String Format Overflow in syslog() Likelihood: High · Severity: Very High
  • CAPEC-135 Format String Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON