How severe is CVE-2024-3273?

CVE-2024-3273 has a CVSS score of 7.3/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2024-3273?

Affected package information for CVE-2024-3273 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2024-3273?

No patch has shipped for CVE-2024-3273 yet — track the dlink dnr-202l firmware advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2024-3273 across my infrastructure?

Inventory every dlink dnr-202l 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.

How do I mitigate CVE-2024-3273 if there is no patch (or I can't update yet)?

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 does O3 Security protect against CVE-2024-3273?

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.

Is CVE-2024-3273 actively exploited in the wild?

Yes. There are 11 known exploit references for CVE-2024-3273, including 7 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-3273?

CVE-2024-3273 has an EPSS (Exploit Prediction Scoring System) score of 100.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2024-3273 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2024-3273 (D-Link Multiple NAS Devices Command Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2024-04-11. CISA required all US federal civilian agencies to remediate this vulnerability by 2024-05-02. The required action was: This vulnerability affects legacy D-Link products. All associated hardware revisions have reached their end-of-life (EOL) or end-of-service (EOS) life cycle and should be retired and replaced per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2024-3273?

CVE-2024-3273 is classified as CWE-77 (CWE-77). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2024-3273?

CVE-2024-3273 affects dlink dnr-202l firmware; dlink dnr-322l firmware; dlink dnr-326 firmware; dlink dns-120 firmware, and 16 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2024-3273?

A Nuclei detection template exists for CVE-2024-3273, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2024-3273 published, and has it been updated?

CVE-2024-3273 was published on April 4, 2024 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2024-04-11 — agencies required to remediate by 2024-05-02

CVE-2024-3273

HIGH

** 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…

Published

Apr 4, 2024

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

11 known

EPSS Exploitation Probability

via FIRST.org ↗

100.0%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

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.

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

20 products · 23 configurations

dnr-202l firmwaredlink

all

dnr-322l firmwaredlink

all

dnr-326 firmwaredlink

all

dns-120 firmwaredlink

all

dns-315l firmwaredlink

all

dns-320 firmwaredlink

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.