CVE-2024-3272 — AI Deep Analysis Summary

Q: Who is affected? (Versions/Components)

🏢 **Vendor**: D-Link (China). 📦 **Affected Products**: DNS-320L, DNS-325, DNS-327, DNS-340L. 📅 **Versions**: Up to 20240403. 🌐 **Category**: D-Link NAS Storage devices.

Q: Is exploitation threshold high? (Auth/Config)

📉 **Threshold**: LOW. 🔓 **Auth**: None required (Unauthenticated). 🌐 **Network**: Network Vector (AV:N). 🚫 **UI**: No user interaction needed (UI:N). 🎯 **Result**: Easy exploitation from anywhere.

Q: Is it fixed officially? (Patch/Mitigation)

🚫 **Official Patch**: NO patch available from D-Link as of April 2024. 📢 **Status**: Vendor has not released a fix. ⏳ **Timeline**: Vulnerability published 2024-04-04 with no official mitigation provided.

Updated May 06, 2026 CVSS 9.8 · Critical

This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis →

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: A critical trust management flaw in D-Link NAS devices. 📉 **Consequences**: Attackers can bypass authentication and execute arbitrary commands remotely.…

Read full answer (login)

Q2Root Cause? (CWE/Flaw)

🛡️ **CWE**: CWE-798 (Use of Hard-coded Credentials). 🔍 **Flaw**: The file `/cgi-bin/nas_sharing.cgi` has a trust management issue.…

Read full answer (login)

Q3Who is affected? (Versions/Components)

🏢 **Vendor**: D-Link (China). 📦 **Affected Products**: DNS-320L, DNS-325, DNS-327, DNS-340L. 📅 **Versions**: Up to 20240403. 🌐 **Category**: D-Link NAS Storage devices.

Q4What can hackers do? (Privileges/Data)

👑 **Privileges**: Root/Admin access via backdoor bypass. 💾 **Data**: Full read/write access to stored files. 🖥️ **Action**: Remote Code Execution (RCE) via command injection.…

Read full answer (login)

Q5Is exploitation threshold high? (Auth/Config)

📉 **Threshold**: LOW. 🔓 **Auth**: None required (Unauthenticated). 🌐 **Network**: Network Vector (AV:N). 🚫 **UI**: No user interaction needed (UI:N). 🎯 **Result**: Easy exploitation from anywhere.

Q6Is there a public Exp? (PoC/Wild Exploitation)

🔥 **Public Exp**: YES. 📂 **Scripts**: GitHub repos like `D-Link-NAS-Devices-Unauthenticated-RCE` and `dinkleberry`. 🧪 **Status**: Active PoCs available.…

Read full answer (login)

Q7How to self-check? (Features/Scanning)

🔍 **Check**: Scan for `/cgi-bin/nas_sharing.cgi`. 🛠️ **Tools**: Use Nuclei templates (`CVE-2024-3272.yaml`). 📡 **Indicator**: Look for hardcoded credential responses when sending `messagebus` to `user` param.…

Read full answer (login)

Q8Is it fixed officially? (Patch/Mitigation)

🚫 **Official Patch**: NO patch available from D-Link as of April 2024. 📢 **Status**: Vendor has not released a fix. ⏳ **Timeline**: Vulnerability published 2024-04-04 with no official mitigation provided.

Q9What if no patch? (Workaround)

🛡️ **Workaround**: Use `Dinkleberry` tool to patch locally. 🔄 **Method**: Swap `nas_sharing.cgi` with NOPs. 📂 **Location**: Modify `/usr/local/config` (since `/usr/local/modules` is read-only).…

Read full answer (login)

Q10Is it urgent? (Priority Suggestion)

🔴 **Priority**: CRITICAL. 🚨 **Urgency**: IMMEDIATE action required. 📉 **Risk**: CVSS 9.8 (Critical). 💡 **Advice**: Apply community patch (`Dinkleberry`) immediately if no vendor fix exists.…

Read full answer (login)

Continue exploring

Vulnerability detail Full AI analysis (login) D-Link CWE-798