CVE-2020-25078
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 · uneditedAn issue was discovered on D-Link DCS-2530L before 1.06.01 Hotfix and DCS-2670L through 2.02 devices. The unauthenticated /config/getuser endpoint allows for remote administrator password disclosure.
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 confidenceThe D-Link DCS-2530L and DCS-2670L camera devices contain an unauthenticated API endpoint at /config/getuser that returns administrator credentials in plaintext, allowing remote attackers to obtain full administrative access without any authentication.
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< 1.04.02< 2.01.10< 2.03.01< 1.03.04< 1.03.02< 2.01.01all versions<= 1.05.05CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify camera modelAccess the device web interface or check the device label to confirm the exact model number (e.g., DCS-2530L, DCS-2670L, DCS-4603, DCS-4622, DCS-4701e, DCS-4703e, DCS-4705e, DCS-4802e, or DCS-P703)Affected if The device is one of the listed affected models
-
Check firmware versionLog into the device web interface and navigate to the System or Settings section to view the firmware version, or use the device's API or telnet/ssh if available to query the firmware versionAffected if The firmware version falls below the threshold for your model (DCS-2530L: >1.05.05, DCS-P703: any version, or other models as listed in the affected ranges)
-
Test vulnerable endpoint accessibilitySend an HTTP GET request to http://<device_ip>/config/getuser without providing any authentication credentials or cookiesAffected if The endpoint responds with HTTP 200 and returns data without requiring authentication
-
Verify credential exposureExamine the response from /config/getuser endpoint and check if it contains plaintext username and password fields, particularly administrator credentialsAffected if The response includes plaintext administrative username and password values
You are affected if your device is a D-Link DCS model listed in the CVE and the /config/getuser endpoint returns plaintext admin credentials without requiring any authentication.
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 · scoped1.03.021.03.041.04.02
Apply vendor-supplied firmware updates (1.06.01 Hotfix for DCS-2530L, and appropriate patch for DCS-2670L). If patches are unavailable, isolate affected devices on a restricted network segment or replace with supported hardware.
DCS 4603: firmware 1.04.02 or higher | DCS 4622: firmware 2.01.10 or higher | DCS 4701e: firmware 2.03.01 or higher | DCS 4703e: firmware 1.03.04 or higher | DCS 4705e: firmware 1.03.02 or higher | DCS 4802e: firmware 2.01.01 or higher | DCS 2530L: firmware 1.06.01 Hotfix or higher | DCS P703: no fi
- 1. Identify the exact D-Link DCS camera model(s) in your environment from the affected list: DCS 4603, DCS 4622, DCS 4701e, DCS 4703e, DCS 4705e, DCS 4802e, DCS P703, or DCS 2530L
- 2. Check the current firmware version of each camera by accessing the web interface or using the manufacturer's discovery tool
- 3. For each affected camera, download the corresponding fixed firmware from D-Link's official support site (support.dlink.com)
- 4. Access each camera's web interface as administrator and navigate to the firmware upgrade or maintenance section
- 5. Upload and apply the appropriate fixed firmware version for your model
- 6. After upgrade, verify the firmware version and confirm the /config/getuser endpoint now requires authentication
- 7. For DCS P703 (no fix available), consider network isolation, restricting access to trusted IPs via firewall, or replacing the device
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-2020-25078 — 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-2020-25078 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