CVE-2020-5880
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 · uneditedOm BIG-IP 15.0.0-15.0.1.3 and 14.1.0-14.1.2.3, the restjavad process may expose a way for attackers to upload arbitrary files on the BIG-IP system, bypassing the authorization system. Resulting error messages may also reveal internal paths of the server.
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 confidenceIn BIG-IP 15.0.0-15.0.1.3 and 14.1.0-14.1.2.3, the restjavad REST Java daemon contains a vulnerability that allows authenticated or unauthenticated attackers to bypass authorization checks and upload arbitrary files to the system. Additionally, error messages generated by this vulnerability can leak internal server paths, potentially aiding further attacks.
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>= 14.1.0, <= 14.1.2.3>= 15.0.0, <= 15.0.1.3>= 14.1.0, <= 14.1.2.3>= 15.0.0, <= 15.0.1.3>= 14.1.0, <= 14.1.2.3>= 15.0.0, <= 15.0.1.3>= 14.1.0, <= 14.1.2.3>= 15.0.0, <= 15.0.1.3>= 14.1.0, <= 14.1.2.3>= 15.0.0, <= 15.0.1.3>= 14.1.0, <= 14.1.2.3>= 15.0.0, <= 15.0.1.3>= 14.1.0, <= 14.1.2.3>= 15.0.0, <= 15.0.1.3>= 14.1.0, <= 14.1.2.3>= 15.0.0, <= 15.0.1.3CVSS 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H
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 installed BIG-IP versionRun 'tmsh show sys version' or check the BIG-IP web UI under System > Software > Image List to view the installed versionAffected if The version falls within 14.1.0-14.1.2.3 or 15.0.0-15.0.1.3
-
Verify restjavad service statusCheck if the restjavad service is running using 'tmsh show sys service restjavad' or by reviewing running processesAffected if The restjavad service is running and accessible (this is the vulnerable component)
-
Inspect logs for unauthorized file upload attemptsReview /var/log/restjavad.log (or equivalent) for entries containing unusual file upload paths, POST requests to upload endpoints, or unexpected file creation eventsAffected if Log entries show unexpected file uploads or requests to upload endpoints that were not initiated by legitimate administrators
-
Check for path leakage in error responsesMonitor HTTP responses from the REST API for error messages that reveal internal server paths such as /var/opt/ or /usr/share/Affected if Error responses expose internal file system paths that should not be visible to users
A system is affected if it runs a vulnerable BIG-IP version (14.1.0-14.1.2.3 or 15.0.0-15.0.1.3) with the restjavad service exposed, and evidence of unauthorized file uploads or path leakage is found in logs or responses.
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.
From vendor dataApply the vendor-supplied patch by upgrading BIG-IP to version 15.1.2.4 or later (for 15.x) and 14.1.2.4 or later (for 14.x). Review access controls and monitor for suspicious file uploads or unusual error messages in logs.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5880 — 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-2020-5880 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