CVE-2013-4977
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 · uneditedBuffer overflow in the RTSP Packet Handler in Hikvision DS-2CD7153-E IP camera with firmware 4.1.0 b130111 (Jan 2013), and possibly other devices, allows remote attackers to cause a denial of service (device crash and reboot) and possibly execute arbitrary code via a long string in the Range header field in an RTSP transaction.
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 the RTSP Packet Handler of Hikvision DS-2CD7153-E IP cameras allows remote attackers to send a specially crafted long string in the Range header field of an RTSP transaction, causing a buffer overflow that leads to device crash/reboot and potential arbitrary code execution.
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= 4.1.0_b130111all versionsCVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 the device modelAccess the camera web interface and navigate to System > Device Information, or use network discovery tools (such as ONVIF Device Manager or Hikvision SADP tool) to confirm the exact model numberAffected if The device model is Hikvision DS-2CD7153-E
-
Check the installed firmware versionIn the camera web interface, go to System > Maintenance > Version Information to view the current firmware build number; alternatively, query the device via SNMP or manufacturer diagnostic toolAffected if The firmware version is 4.1.0_b130111 or any other version (the advisory indicates all versions are affected)
-
Verify RTSP service is enabledLog into the camera web interface and navigate to Network > RTSP or Streaming Protocol settings to confirm whether RTSP is turned on; also check if RTSP port (default 554) is listening on the deviceAffected if RTSP protocol is enabled and accessible on the device
-
Confirm RTSP is network-accessiblePerform a port scan of the camera IP address targeting TCP ports 554 and 8554, or attempt an RTSP connection from an external system to determine if the RTSP service is exposed beyond the local networkAffected if The RTSP service is exposed to untrusted networks or the internet
You are affected if you have a Hikvision DS-2CD7153-E camera with any firmware version where RTSP is enabled and network-accessible, as the vulnerability triggers via a specially crafted Range header in RTSP transactions.
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.
From vendor dataApply available firmware update from Hikvision for affected devices; if no update exists, network-segment affected cameras and disable RTSP if not required, or replace vulnerable devices.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4977 — 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-2013-4977 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