CVE-2024-3273
HIGHCVE-2024-3273 is a high-severity (CVSS 7.3) CWE-77 vulnerability in dlink dns-320l firmware. It is in CISA's Known Exploited Vulnerabilities catalog (added 2024-04-11) — treat it as actively exploited and patch now. O3 Security detects and blocks CVE-2024-3273 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as critical, was found in D-Link DNS-320L, DNS-325, DNS-327L and DNS-340L up to 20240403. Affected is an unknown…
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2024-04-11. Federal agencies were required to remediate by 2024-05-02.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2024-3273.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-3273 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.
Where this sits among everything scored
Of 368,770 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Description
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as critical, was found in D-Link DNS-320L, DNS-325, DNS-327L and DNS-340L up to 20240403. Affected is an unknown function of the file /cgi-bin/nas_sharing.cgi of the component HTTP GET Request Handler. The manipulation of the argument system leads to command injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-259284. 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.
Affected Products
dns-320l firmwaredlinkdns-325 firmwaredlinkdns-327l firmwaredlinkdns-340l firmwaredlinkResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as…
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as…
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as…
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as…
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as…
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as…
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as…
Detection & mitigation playbook
Vendor / applianceDetect
Inventory every dlink dns-320l firmware deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Remediation status
No patch has shipped for CVE-2024-3273 yet — track the dlink dns-320l firmware advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2024-3273 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.
Tailored to CVE-2024-3273. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-3273 being exploited in your environment?
O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2024-3273 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.