Apache on Red Hat Linux with with the UserDir directive enabled generates different error codes when a username exists…
The flaw lies in Apache on Red Hat Linux when the UserDir directive is enabled: the server returns different error codes depending on whether a username exists but has no public_html directory, versus whether the username does not exist at all. An attacker with remote network access can send requests to the server and use these differing responses to determine which usernames are valid, with no authentication or user interaction required.
Apache on Red Hat Linux with with the UserDir directive enabled generates different error codes when a username exists and there is no public_html directory and when the username does not exist, which could allow remote attackers to determine valid usernames on the server.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Public exploit code (Exploit-DB) was available 5 months before disclosure.
- Public exploit codeExploit-DB5 mo before
- Disclosedday 0
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
No techniques linkedNo ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.
What security researchers reported
Not named in any threat report yetAlso mentioned in 1 community threat pulse (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.