CertificationApplication · Redhat
CVE-2018-10869
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 · uneditedredhat-certification does not properly restrict files that can be download through the /download page. A remote attacker may download any file accessible by the user running httpd.
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 confidenceA path traversal vulnerability in redhat-certification allows remote attackers to download arbitrary files accessible by the httpd user through the /download page by manipulating file paths (e.g., using ../../../etc/passwd). The application fails to validate or sanitize user-supplied path inputs before serving files.
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
CertificationApplication
all versions
Enterprise LinuxOperating system
= 7.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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Confirm redhat-certification is installedCheck for the redhat-certification package or service using 'rpm -qa | grep -i redhat-certification' or 'systemctl list-units | grep certification'Affected if The package or service is found on the system
-
Verify the product versionRun 'rpm -qi redhat-certification' or check the installed version through the package managerAffected if The installed version falls within 'all versions' for Redhat Certification or equals 7.0 for RHEL
-
Confirm httpd service is runningRun 'systemctl status httpd' or 'ps aux | grep httpd' to verify the Apache/httpd process is activeAffected if httpd is running and serving the redhat-certification application
-
Check if /download endpoint is accessibleAttempt to access the /download path through the web application or check the web server configuration for the /download route handlerAffected if The /download endpoint exists and accepts path parameters
-
Verify path traversal is possibleTest the /download endpoint with a path like '../../../etc/passwd' or similar to see if arbitrary file retrieval is permitted (requires authorization if testing in production)Affected if The application returns file contents outside the intended download directory
The system is affected if redhat-certification is installed on RHEL 7.0 or any version of Redhat Certification, httpd is serving the application, and the /download endpoint allows path traversal to access files beyond the intended directory.
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 dataImplement strict input validation on the /download endpoint to restrict file access to intended directories only. Use allow-listed file patterns, resolve paths canonically, and verify the final resolved path is within an approved directory before serving files.
Fix this in Certification
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10869 — 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-2018-10869 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