CVE-2020-24626
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 · uneditedUnathenticated directory traversal in the ReceiverServlet class doPost() method can lead to arbitrary remote code execution in HPE Pay Per Use (PPU) Utility Computing Service (UCS) Meter version 1.9.
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 confidenceUnauthenticated directory traversal vulnerability in the ReceiverServlet class doPost() method allows attackers to manipulate file paths and potentially write/execute arbitrary code on the HPE Pay Per Use (PPU) UCS Meter v1.9. The lack of authentication combined with path traversal enables remote code execution without any credentials.
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= 1.9CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 HPE PPU UCS Meter installationLocate the installation directory for HPE Utility Computing Service Meter or HPE Pay Per Use UCS Meter v1.9. Check for files named 'ReceiverServlet' or 'receiver-servlet' within the application directory structure.Affected if The product HPE PPU UCS Meter v1.9 is installed and the ReceiverServlet class exists in the application.
-
Verify the ReceiverServlet endpoint is exposedCheck the application's web.xml deployment descriptor or equivalent servlet mapping configuration for a servlet mapped to '/ReceiverServlet' or similar path that handles POST requests.Affected if The ReceiverServlet is mapped and accessible via HTTP/HTTPS POST requests without authentication.
-
Confirm authentication is not enforced on ReceiverServletReview the application's security configuration (web.xml security constraints, spring security config, or equivalent) to determine if authentication is required for the ReceiverServlet endpoint.Affected if No authentication constraint is defined for the ReceiverServlet endpoint, allowing unauthenticated access.
-
Check doPost() method for path traversal handlingIf source code or decompiled bytecode is available, inspect the doPost() method in ReceiverServlet class to see if it performs path validation or sanitization on file path parameters.Affected if The doPost() method accepts user-controlled file paths without proper validation, allowing '..' sequences to traverse directories.
You are affected if HPE PPU UCS Meter v1.9 is installed and the ReceiverServlet endpoint is accessible without authentication, allowing unauthenticated attackers to manipulate file paths via directory traversal.
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 dataImmediately restrict network access to the vulnerable ReceiverServlet endpoint. Apply vendor-supplied patch for HPE PPU UCS Meter v1.9. If no patch available, implement strict input validation and path sanitization in the doPost() method to block traversal sequences.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24626 — 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-24626 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