Big Ip Access Policy ManagerApplication · F5

CVE-2013-0150

HIGH · 9.3 CVSS v2.0 Published 2013-08-09
Fix available
A fix is available. Upgrade to after 11.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Directory traversal vulnerability in a signed Java applet within F5 BIG-IP APM and FirePass client-side components allows remote attackers to upload and execute arbitrary files by inserting '..' (dot-dot) sequences into the filename parameter during file upload operations.

MitigationApply F5 security patches or upgrade BIG-IP APM to 10.2.5+/11.4.0+ and FirePass to 7.0.1+ to remediate the directory traversal in the signed Java applet.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Big Ip Access Policy ManagerApplication
Affected:>= 10.1.0, <= 10.2.4>= 11.0.0, <= 11.3.0
Big Ip Advanced Firewall ManagerApplication
Affected:= 11.3.0
Big Ip AnalyticsApplication
Affected:>= 11.0.0, <= 11.3.0
Big Ip Application Security ManagerApplication
Affected:>= 10.1.0, <= 10.2.4>= 11.0.0, <= 11.3.0
Big Ip Edge GatewayWeb browser
Affected:>= 10.1.0, <= 10.2.4>= 11.0.0, <= 11.3.0
Big Ip Global Traffic ManagerApplication
Affected:>= 10.1.0, <= 10.2.4>= 11.0.0, <= 11.3.0
Big Ip Link ControllerApplication
Affected:>= 10.1.0, <= 10.2.4>= 11.0.0, <= 11.3.0
Big Ip Local Traffic ManagerApplication
Affected:>= 10.1.0, <= 10.2.4>= 11.0.0, <= 11.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed F5 BIG-IP product and version
    Run 'tmsh show sys version' or check the BIG-IP GUI System > Overview page to determine the product module and version number
    Affected if The product is one of APM, AFM, Analytics, ASM, Edge Gateway, GTM, LC, or LTM and the version falls within 10.1.0-10.2.4 or 11.0.0-11.3.0
  2. Confirm the Access Policy Manager (APM) module is provisioned
    Run 'tmsh show sys provision' or check System > Resource Provisioning in the GUI to see if APM is provisioned
    Affected if APM module is provisioned on an affected version (APM is specifically cited as the primary affected product)
  3. Verify Java applet-based client access is in use
    Check if users connect via the Java-based VPN client applet (APM client or FirePass SSL VPN web access). Inspect /config/bigip_apm or /config/bigip.conf for APM client profile configurations containing Java applet settings
    Affected if Java applet client profiles are configured and enabled for end-user access

The environment is affected if the installed BIG-IP product version is within 10.1.0-10.2.4 or 11.0.0-11.3.0 and the APM module with Java applet client access is provisioned/enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 11.3.0
Interim mitigation

Apply F5 security patches or upgrade BIG-IP APM to 10.2.5+/11.4.0+ and FirePass to 7.0.1+ to remediate the directory traversal in the signed Java applet.

Recommended fix High confidence

Upgrade to BIG‑IP APM 10.2.5 (or later) for 10.x; upgrade to 11.4.0 (or later) for 11.x

  1. Obtain the fixed BIG-IP software image from F5 Support (e.g., BIG‑IP APM 10.2.5 for 10.x or 11.4.0 for 11.x) that includes the patch for CVE‑2013‑0150.
  2. Back up the current configuration by creating a UCS archive (use 'tmsh save sys ucs <backup_name>' or the GUI).
  3. Upload the new software image to the BIG‑IP device (via GUI: System > Software Management > Upload, or secure copy).
  4. Install the image to a new volume (GUI: Software Management > Install, or CLI: 'tmsh install sys software <image> <volume>').
  5. Reboot the device into the new volume (GUI: Software Management > Boot, or CLI: 'tmsh boot system volume <volume>').
  6. After the system comes up, verify the version with 'tmsh show sys version' or the GUI, confirming that the Java applet has been updated.
  7. Test that the directory‑traversal issue is fixed (e.g., ensure the signed Java applet no longer accepts '..' in the filename), or review the release notes for confirmation.
  8. Optionally, remove the old volume to free disk space after a successful upgrade.
Caveat Review release notes; some configuration or behavioral changes may occur when moving to 10.2.5/11.4.0.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0150 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0150 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data