CVE-2013-0150
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 · uneditedDirectory 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 confidenceDirectory 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.
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>= 10.1.0, <= 10.2.4>= 11.0.0, <= 11.3.0= 11.3.0>= 11.0.0, <= 11.3.0>= 10.1.0, <= 10.2.4>= 11.0.0, <= 11.3.0>= 10.1.0, <= 10.2.4>= 11.0.0, <= 11.3.0>= 10.1.0, <= 10.2.4>= 11.0.0, <= 11.3.0>= 10.1.0, <= 10.2.4>= 11.0.0, <= 11.3.0>= 10.1.0, <= 10.2.4>= 11.0.0, <= 11.3.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed F5 BIG-IP product and versionRun 'tmsh show sys version' or check the BIG-IP GUI System > Overview page to determine the product module and version numberAffected 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
-
Confirm the Access Policy Manager (APM) module is provisionedRun 'tmsh show sys provision' or check System > Resource Provisioning in the GUI to see if APM is provisionedAffected if APM module is provisioned on an affected version (APM is specifically cited as the primary affected product)
-
Verify Java applet-based client access is in useCheck 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 settingsAffected 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.
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 · scopedApply 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.
Upgrade to BIG‑IP APM 10.2.5 (or later) for 10.x; upgrade to 11.4.0 (or later) for 11.x
- 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.
- Back up the current configuration by creating a UCS archive (use 'tmsh save sys ucs <backup_name>' or the GUI).
- Upload the new software image to the BIG‑IP device (via GUI: System > Software Management > Upload, or secure copy).
- Install the image to a new volume (GUI: Software Management > Install, or CLI: 'tmsh install sys software <image> <volume>').
- Reboot the device into the new volume (GUI: Software Management > Boot, or CLI: 'tmsh boot system volume <volume>').
- After the system comes up, verify the version with 'tmsh show sys version' or the GUI, confirming that the Java applet has been updated.
- 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.
- Optionally, remove the old volume to free disk space after a successful upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
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 locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-0150 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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