cve.bz

CVE-2013-0150 f5: Path traversal

no score yetEPSS 6.3%

f5: no CVSS score yet. EPSS 6.3% estimated probability of exploitation activity in the next 30 days.

On this page
Directory traversal vulnerability in an unspecified signed Java applet in the client-side components in F5 BIG-IP APM 10.1.0 through 10.2.4 and 11.0.0 through 11.3.0, FirePass 6.0.0 through 6.1.0 and 7.0.0, and other products "when APM is provisioned," allows remote attackers to upload and execute arbitrary files via a .. (dot dot) in the filename parameter.
EPSS
6.3% (unchanged from 6.3% a week ago; 6.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 94th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
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-2013-0150 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2013-0150?via=ask-ai-copy and https://cve.bz/cve/CVE-2013-0150?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-2013-0150 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
f5:big-ip_access_policy_managerfrom 10.1.0 through 10.2.4
f5:big-ip_access_policy_managerfrom 11.0.0 through 11.3.0
f5:big-ip_advanced_firewall_manager11.3.0
f5:big-ip_analyticsfrom 11.0.0 through 11.3.0
f5:big-ip_application_security_managerfrom 10.1.0 through 10.2.4
f5:big-ip_application_security_managerfrom 11.0.0 through 11.3.0
f5:big-ip_edge_gatewayfrom 10.1.0 through 10.2.4
f5:big-ip_edge_gatewayfrom 11.0.0 through 11.3.0
f5:big-ip_global_traffic_managerfrom 10.1.0 through 10.2.4
f5:big-ip_global_traffic_managerfrom 11.0.0 through 11.3.0
f5:big-ip_link_controllerfrom 10.1.0 through 10.2.4
f5:big-ip_link_controllerfrom 11.0.0 through 11.3.0
f5:big-ip_local_traffic_managerfrom 10.1.0 through 10.2.4
f5:big-ip_local_traffic_managerfrom 11.0.0 through 11.3.0
f5:big-ip_policy_enforcement_manager11.3.0
f5:big-ip_protocol_security_modulefrom 10.1.0 through 10.2.4
f5:big-ip_protocol_security_modulefrom 11.0.0 through 11.3.0
f5:big-ip_wan_optimization_managerfrom 10.1.0 through 10.2.4
f5:big-ip_wan_optimization_managerfrom 11.0.0 through 11.3.0
f5:big-ip_webacceleratorfrom 10.1.0 through 10.2.4
f5:big-ip_webacceleratorfrom 11.0.0 through 11.3.0
f5:firepassfrom 6.0.0 through 6.1.0
f5:firepass7.0.0

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

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

References

Check your stackJSON