CVE-2013-3613

NONECVSS 0.0Trending — 3 sources updated this weekElevated

0.0

Dahua DVR appliances do not properly restrict UPnP requests, which makes it easier for remote attackers to obtain access via vectors involving a replay attack against the TELNET port.

CVSS v3: —
EG Score: 0.0(none)
EPSS: 93.9%
KEV: Not listed

Published

September 17, 2013

Last Modified

April 29, 2026

References (2)

cret@certhttp://www.kb.cert.org/vuls/id/800094
af854a3a-2127-422b-91ae-364da2661108http://www.kb.cert.org/vuls/id/800094

Weakness Classification(1)

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

CWE-287Improper Authentication

Data Freshness Timeline

(refreshed 15× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:10 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 22:27 UTCEG score recompute
2026-05-28 22:27 UTCGHSA enrichment
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 07:16 UTCepss_batch

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-29673
First seen Nov 18, 2013
Dahua DVR 2.608.0000.0/2.608.GV00.0 - Authentication Bypass (Metasploit)
Open source ↗

Frequently asked(4)

What is CVE-2013-3613?

CVE-2013-3613 is a none vulnerability published on September 17, 2013. Dahua DVR appliances do not properly restrict UPnP requests, which makes it easier for remote attackers to obtain access via vectors involving a replay attack against the TELNET port.

When was CVE-2013-3613 disclosed?

CVE-2013-3613 was first published in the National Vulnerability Database on September 17, 2013, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2013-3613 actively exploited?

CVE-2013-3613 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 93.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2013-3613?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-3613, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-3613

Explore →

Is Your Infrastructure Affected by CVE-2013-3613?

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

Start Free Scan →Browse All CVEs

CVE-2013-3613

📅 Published

🔄 Last Modified

🔗 References (2)

Weakness Classification(1)

Data Freshness Timeline

Publicly available exploits

❓ Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2013-3613?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (2)

Frequently asked(4)

Related CVEs(same CWE)