CVE-2013-1602

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 15.1%, top 4% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 15%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An Information Disclosure vulnerability exists due to insufficient validation of authentication cookies for the RTSP session in D-Link DCS-5635 1.01, DCS-1100L 1.04, DCS-1130L 1.04, DCS-1100 1.03/1.04_US, DCS-1130 1.03/1.04_US , DCS-2102 1.05_RU/1.06/1.06_FR/1.05_TESCO, DCS-2121 1.05_RU/1.06/1.06_FR/1.05_TESCO, DCS-3410 1.02, DCS-5230 1.02, DCS-5230L 1.02, DCS-6410 1.0, DCS-7410 1.0, DCS-7510 1.0, and WCS-1100 1.02, which could let a malicious user obtain unauthorized access to video streams.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
64(Track)
EG Risk 64/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
96.4%
KEV
Not listed

Published

January 28, 2020

Last Modified

November 21, 2024

References (8)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:14 UTCEPSS rescore
  2. 2026-07-23 01:09 UTCEG score recompute
  3. 2026-07-23 00:12 UTCEG score recompute
  4. 2026-07-22 21:51 UTCEG score recompute
  5. 2026-07-22 14:04 UTCEPSS rescore
  6. 2026-07-22 14:04 UTCEPSS rescore
  7. 2026-07-21 15:21 UTCEPSS rescore
  8. 2026-07-20 17:03 UTCEPSS rescore
  9. 2026-07-20 17:03 UTCEPSS rescore
  10. 2026-07-19 02:25 UTCEPSS rescore
  11. 2026-07-19 02:25 UTCEPSS rescore
  12. 2026-07-18 10:00 UTCEPSS rescore
  13. 2026-07-16 16:58 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-15 16:54 UTCEPSS rescore
  16. 2026-07-15 01:56 UTCEPSS rescore
  17. 2026-07-13 22:26 UTCEPSS rescore
  18. 2026-07-13 06:08 UTCEPSS rescore
  19. 2026-07-11 08:23 UTCEPSS rescore
  20. 2026-07-09 19:05 UTCEPSS rescore
  21. 2026-07-08 15:10 UTCEPSS rescore
  22. 2026-07-06 02:19 UTCEPSS rescore
  23. 2026-07-06 02:19 UTCEPSS rescore
  24. 2026-07-05 02:26 UTCEPSS rescore
  25. 2026-07-04 06:27 UTCEPSS rescore
Show 51 more
  1. 2026-07-01 15:02 UTCEPSS rescore
  2. 2026-06-30 23:19 UTCEPSS rescore
  3. 2026-06-30 23:19 UTCEPSS rescore
  4. 2026-06-29 14:02 UTCEPSS rescore
  5. 2026-06-28 14:03 UTCEPSS rescore
  6. 2026-06-28 04:53 UTCEPSS rescore
  7. 2026-06-28 04:53 UTCEPSS rescore
  8. 2026-06-27 03:05 UTCEPSS rescore
  9. 2026-06-25 13:46 UTCEPSS rescore
  10. 2026-06-24 14:02 UTCEPSS rescore
  11. 2026-06-24 14:02 UTCEPSS rescore
  12. 2026-06-23 21:30 UTCEPSS rescore
  13. 2026-06-21 01:57 UTCEPSS rescore
  14. 2026-06-21 01:56 UTCEPSS rescore
  15. 2026-06-19 19:23 UTCEPSS rescore
  16. 2026-06-19 19:22 UTCEPSS rescore
  17. 2026-06-18 17:49 UTCEPSS rescore
  18. 2026-06-18 17:49 UTCEPSS rescore
  19. 2026-06-17 17:49 UTCEPSS rescore
  20. 2026-06-17 17:49 UTCEPSS rescore
  21. 2026-06-16 17:49 UTCEPSS rescore
  22. 2026-06-16 17:49 UTCEPSS rescore
  23. 2026-06-15 17:44 UTCEPSS rescore
  24. 2026-06-13 22:57 UTCEPSS rescore
  25. 2026-06-12 23:08 UTCEPSS rescore
  26. 2026-06-11 13:56 UTCEPSS rescore
  27. 2026-06-10 13:18 UTCEPSS rescore
  28. 2026-06-08 14:14 UTCEPSS rescore
  29. 2026-06-07 15:22 UTCEPSS rescore
  30. 2026-06-06 13:45 UTCEPSS rescore
  31. 2026-06-06 13:45 UTCEPSS rescore
  32. 2026-06-05 22:44 UTCEPSS rescore
  33. 2026-06-05 22:44 UTCEPSS rescore
  34. 2026-06-05 06:08 UTCEPSS rescore
  35. 2026-06-05 06:08 UTCEPSS rescore
  36. 2026-06-02 20:10 UTCEPSS rescore
  37. 2026-06-02 20:10 UTCEPSS rescore
  38. 2026-06-01 13:49 UTCEPSS rescore
  39. 2026-06-01 13:49 UTCEPSS rescore
  40. 2026-05-31 00:14 UTCEPSS rescore
  41. 2026-05-31 00:14 UTCEPSS rescore
  42. 2026-05-29 13:41 UTCEPSS rescore
  43. 2026-05-29 13:41 UTCEPSS rescore
  44. 2026-05-28 13:42 UTCEPSS rescore
  45. 2026-05-28 13:42 UTCEPSS rescore
  46. 2026-05-28 13:42 UTCEPSS rescore
  47. 2026-05-27 13:38 UTCEPSS rescore
  48. 2026-05-27 13:38 UTCEPSS rescore
  49. 2026-05-27 08:29 UTCEG score recompute
  50. 2026-05-27 08:29 UTCGHSA enrichment
  51. 2026-05-24 16:43 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-25138✓ verified
    First seen May 1, 2013

    D-Link IP Cameras - Multiple Vulnerabilities

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2013-1602?
CVE-2013-1602 is a high vulnerability published on January 28, 2020. An Information Disclosure vulnerability exists due to insufficient validation of authentication cookies for the RTSP session in D-Link DCS-5635 1.01, DCS-1100L 1.04, DCS-1130L 1.04, DCS-1100 1.03/1.04US, DCS-1130 1.03/1.04US , DCS-2102 1.05RU/1.06/1.06FR/1.05TESCO, DCS-2121…
When was CVE-2013-1602 disclosed?
CVE-2013-1602 was first published in the National Vulnerability Database on January 28, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-1602 actively exploited?
CVE-2013-1602 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2013-1602?
CVE-2013-1602 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2013-1602?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-1602, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2013-1602

Explore →

Is Your Infrastructure Affected by CVE-2013-1602?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs