CertificationApplication · Redhat
CVE-2018-10863
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 · uneditedIt was discovered that redhat-certification 7 is not properly configured and it lists all files and directories in the /var/www/rhcert/store/transfer directory, through the /rhcert-transfer URL. An unauthorized attacker may use this flaw to gather sensible information.
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 confidenceredhat-certification 7 has a directory listing vulnerability where the web server exposes the contents of /var/www/rhcert/store/transfer through the /rhcert-transfer URL, allowing unauthorized users to view all files and directories in that location.
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
= 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.1/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.
-
Identify installed redhat-certification versionRun the package manager or application to determine the installed version of redhat-certification (for example: rpm -q redhat-certification, or check via the application itself if a version command is available)Affected if The installed version is 7.0 (exact match)
-
Confirm the vulnerable directory existsCheck for the presence of /var/www/rhcert/store/transfer directory on the system using: ls -la /var/www/rhcert/store/transferAffected if The directory /var/www/rhcert/store/transfer exists on the system
-
Verify the web server exposes the transfer pathCheck the web server configuration (such as Apache or Nginx config files in /etc/httpd or /etc/nginx) for anyAlias or location block mapping /rhcert-transfer to /var/www/rhcert/store/transferAffected if The web server is configured to serve /rhcert-transfer pointing to the transfer directory
-
Confirm directory listing is enabledWith the web server running, attempt to access http://yourhostname/rhcert-transfer via curl or a browser and verify whether directory listing (showing file/folder listings) is returned instead of a 403 Forbidden or an index fileAffected if Accessing /rhcert-transfer displays a directory listing of files and folders rather than denying access or loading an index file
You are affected if redhat-certification version 7.0 is installed, the /var/www/rhcert/store/transfer directory exists, the web server serves it via /rhcert-transfer, and directory listing is enabled for that path.
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 dataConfigure the web server to disable directory listing for the /var/www/rhcert/store/transfer directory, or remove the transfer directory if not required for production operation.
Fix this in Certification
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10863 — 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-10863 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