Skip to content
Fencer Intel
critical 9.1

CVE-2018-10867 json

Files are accessible without restrictions from the /update/results page of redhat-certification 7 package, allowing an attacker to remove a…

published 5y ago modified 4mo ago also EUVD-2018-2933

cvss
9.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits
0
none known

Summary

Files are accessible without restrictions from the /update/results page of redhat-certification 7 package, allowing an attacker to remove any file accessible by the apached user.

Is CVE-2018-10867 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-10867 updated cvss 6.5

redhat-certification: /uploads/results page allows to remove files

  • Red Hat Certification for Red Hat Enterprise Linux 7 redhat-certification
    affected: workaround, no fix available “If SELinux is enabled, it will restrict the number of files accessible by the httpd process.”
  • Red Hat Certification for Red Hat Enterprise Linux 6 redhat-certification
    not affected: vulnerable code not present “If SELinux is enabled, it will restrict the number of files accessible by the httpd process.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.07% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:N/I:P/A:P

Affected products

  • n/a redhat-certification

Classification

Weakness
  • CWE-552 Files or Directories Accessible to External Parties

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.