dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 29 Sep 2022.
Dir 300 FirmwareOperating system · Dlink

CVE-2011-4723

MEDIUM · 5.7 CVSS v3.1 Published 2011-12-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click

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
The D-Link DIR-300 router stores cleartext passwords, which allows context-dependent attackers to obtain sensitive information via unspecified vectors.

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 · moderate confidence

The D-Link DIR-300 router stores passwords in cleartext rather than using proper hashing or encryption. This allows attackers with access to the router's configuration or filesystem to read sensitive credentials (likely admin passwords) in plaintext. The exact attack vector is unspecified in the advisory.

MitigationIf the router is still in production, replace it with a supported device as the DIR-300 is end-of-life and unlikely to receive firmware patches. If continued use is unavoidable, restrict all access to the router's management interface via firewall rules and monitor for unauthorized access attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dir 300 FirmwareOperating system
Affected:all versions

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is D-Link DIR-300
    Access the router's web administration interface and navigate to the Status or System Information page to identify the exact model number and firmware version, or check the device label on the router hardware itself
    Affected if The device is a D-Link DIR-300 router running any firmware version
  2. Locate the router configuration storage
    Access the router's configuration file either through the web interface (typically under System > Configuration > Backup/Restore), or via SSH/Telnet access to the device filesystem if enabled
    Affected if You are able to obtain a backup of the router configuration file or access the device filesystem
  3. Examine stored credentials in configuration
    Open the configuration file (often .bin, .cfg, or XML format) in a text editor and search for password-related fields such as 'password', 'adminpass', or similar entries. Look for plaintext strings that appear to be credentials rather than hashed or encrypted values
    Affected if Password values in the configuration appear as readable plaintext strings rather than hexadecimal hashes or encrypted blobs

If the device is a D-Link DIR-300 and stored password entries in its configuration file are readable as plaintext strings, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If the router is still in production, replace it with a supported device as the DIR-300 is end-of-life and unlikely to receive firmware patches. If continued use is unavoidable, restrict all access to the router's management interface via firewall rules and monitor for unauthorized access attempts.

Recommended fix Moderate confidence
  1. Since D-Link DIR-300 firmware is no longer supported and no specific fixed version is identified in available sources, the recommended mitigation is to replace the end-of-life router with a currently supported model.
  2. If replacement is not immediately possible, ensure the router is placed behind a modern firewall and not exposed directly to the internet.
  3. Change default administrative credentials to strong, unique passwords.
  4. Disable any remote management interfaces (WAN access) if not needed.
  5. Monitor network traffic for unusual activity that could indicate credential compromise.
Caveat This is an end-of-life device with no firmware updates available; replacement with a supported router is the recommended long-term solution

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dir 300 Firmware Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-4723 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-4723 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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