sfewer-r7 9c075c7cce Previously the check routine only leveraged the first vuln in the chain, CVE-2023-20198, to perform a version based check. However the second vuln in the chain, CVE-2023-20273, was not verified as to working, so a return code of CheckCode::Vulnerable may no have been acurate if the target was vulnerable to CVE-2023-20198 but not CVE-2023-20273. Now we leverage both CVE-2023-20198 and CVE-2023-20273 to ensure the target is actually vulnerable. For example, it has been observed that the C8000v series appliance version 17.6.5 is vulnerable to CVE-2023-20198, but not vulnerable to CVE-2023-20273, even though the IOS-XE version indicates they should be vulnerable to CVE-2023-20273. As this exploit chains both CVE-2023-20198 and CVE-2023-20273 together, the check routine must verify both CVEs work as expected in order to return CheckCode::Vulnerable (i.e. we cannot solely rely on a version based check via CVE-2023-20198).

2025-03-03 20:29:20 +00:00

..

antivirus

…

browser

…

fileformat

change nil guards to default values, nil or blank guards for certain datastore options

2024-05-29 09:34:58 -05:00

ftp

…

games

…

http

Land #19899, D-Tale remote code execution module

2025-03-03 13:04:45 +01:00

ids

…

imap

…

local

Remove errant CVE reference.

2025-02-20 08:19:23 -06:00

misc

Previously the check routine only leveraged the first vuln in the chain, CVE-2023-20198, to perform a version based check. However the second vuln in the chain, CVE-2023-20273, was not verified as to working, so a return code of CheckCode::Vulnerable may no have been acurate if the target was vulnerable to CVE-2023-20198 but not CVE-2023-20273. Now we leverage both CVE-2023-20198 and CVE-2023-20273 to ensure the target is actually vulnerable. For example, it has been observed that the C8000v series appliance version 17.6.5 is vulnerable to CVE-2023-20198, but not vulnerable to CVE-2023-20273, even though the IOS-XE version indicates they should be vulnerable to CVE-2023-20273. As this exploit chains both CVE-2023-20198 and CVE-2023-20273 together, the check routine must verify both CVEs work as expected in order to return CheckCode::Vulnerable (i.e. we cannot solely rely on a version based check via CVE-2023-20198).

2025-03-03 20:29:20 +00:00

mysql

Update broken secunia references

2023-03-23 10:43:57 +00:00

pop3

…

postgres

Align SQL sessions peerhost and peerport

2024-03-04 13:11:32 +00:00

pptp

…

proxy

…

redis

Run rubocop on exploit modules

2023-02-08 15:20:32 +00:00

samba

Replace deprecated File.exists? with File.exist?

2023-03-05 14:30:47 +11:00

smtp

Removed "ssl_restore = true"

2024-07-26 17:30:25 +02:00

snmp

…

ssh

Add error_callback to SSH Command Stream

2024-11-25 16:43:59 +00:00

telnet

…

upnp

Update deprecation date and message

2023-12-05 10:51:12 +01:00