CVE-2024-7849
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as critical, was found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326, DNS-340L, DNS-343, DNS-345, DNS-726-4, DNS-1100-4, DNS-1200-05 and DNS-1550-04 up to 20240814. This affects the function cgi_create_album of the file /cgi-bin/photocenter_mgr.cgi. The manipulation of the argument current_path leads to buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. NOTE: Vendor was contacted early and confirmed that the product is end-of-life. It should be retired and replaced.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBuffer overflow vulnerability in D-Link NAS devices (multiple models) in the cgi_create_album function of photocenter_mgr.cgi. The current_path argument is not properly bounds-checked, allowing an attacker to overflow the buffer and potentially achieve remote code execution. The CVSS 8.8 indicates low attack complexity with high exploitability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify D-Link NAS device modelAccess the device web interface or check the device label/menu for the exact model number (e.g., DNS-320, DNS-325, DNS-340L, etc.)Affected if The device is one of the affected D-Link NAS models listed in the product compatibility documentation for this CVE
-
Verify photocenter_mgr.cgi is presentAttempt to access the CGI binary via HTTP/HTTPS (e.g., http://<device-ip>/cgi-bin/photocenter_mgr.cgi) or check the device firmware filesystem if shell access is availableAffected if The photocenter_mgr.cgi file exists and is accessible on the device
-
Confirm photo center feature is enabledCheck the device web interface under Applications or Photo Center settings to see if the photo album/center feature is turned onAffected if The photo center or photo album feature is enabled in the device configuration
-
Check network exposureDetermine if the device management interface (HTTP/HTTPS ports 80/443) is exposed to the internet or untrusted networks by reviewing firewall rules, port forwarding configurations, or router NAT settingsAffected if The device is directly accessible from the internet or from untrusted network segments
-
Review access logs for photocenter_mgr.cgiIf logging is enabled, examine web server access logs or device logs for requests to the cgi_create_album function or unusual activity targeting photocenter_mgr.cgiAffected if There are anomalous or suspicious requests to the vulnerable CGI endpoint in the logs
The environment is affected if it contains an end-of-life D-Link NAS device with the photocenter_mgr.cgi interface exposed to untrusted networks and the photo center feature enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedThese are end-of-life products with no vendor patches available. The devices should be retired and replaced. If immediate replacement is not possible, network isolation and restricting access to trusted IP addresses only may reduce exposure.
- These D-Link devices (DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326, DNS-340L, DNS-343, DNS-345, DNS-726-4, DNS-1100-4, DNS-1200-05, DNS-1550-04) are end-of-life and no longer supported by D-Link. No security patches or firmware updates will be released.
- Replace the affected devices with newer, actively supported hardware from D-Link or an alternative vendor.
- If immediate replacement is not possible, disable the photocenter_mgr.cgi CGI functionality or the entire photo center feature if not required.
- If the photo center feature is required, implement network segmentation (VLAN) to isolate these devices from untrusted networks.
- Configure firewall rules to block external access to the device's web interface (ports 80/443) from the internet.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7849 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-7849 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data