CVE-2007-4747
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 · uneditedThe telnet service in Cisco Video Surveillance IP Gateway Encoder/Decoder (Standalone and Module) firmware 1.8.1 and earlier, Video Surveillance SP/ISP Decoder Software firmware 1.11.0 and earlier, and the Video Surveillance SP/ISP firmware 1.23.7 and earlier does not require authentication, which allows remote attackers to perform administrative actions, aka CSCsj31729.
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 telnet service in Cisco Video Surveillance IP Gateway Encoder/Decoder firmware 1.8.1 and earlier, Decoder Software 1.11.0 and earlier, and SP/ISP firmware 1.23.7 and earlier lacks authentication, allowing remote unauthenticated attackers to gain administrative access.
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.8.1<= 1.11.0<= 1.23.7CVSS 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.
-
Verify telnet service accessibilityScan the target device for open telnet port (TCP 23). Use 'nc -zv <target_ip> 23' or nmap -p 23 <target_ip> to check if telnet port is listening and accessible from the network.Affected if Telnet port 23 is open and reachable on the Cisco Video Surveillance device.
-
Identify firmware versionAccess the device web interface or CLI and retrieve the firmware/software version. In the web interface, navigate to System or About page. Via CLI, use 'show version' or check the firmware file name displayed at boot.Affected if You can retrieve a firmware version number from the device.
-
Compare version to affected rangesMatch the retrieved version against these vulnerable ranges: Encoder/Decoder firmware <= 1.8.1, Decoder Software <= 1.11.0, SP/ISP firmware <= 1.23.7. Note that version formats may vary (e.g., 1.8.1, 1.8, 1.8.0).Affected if The installed firmware version is 1.8.1 or lower for Encoder/Decoder, 1.11.0 or lower for Decoder Software, or 1.23.7 or lower for SP/ISP firmware.
The device is affected if telnet port 23 is exposed and the installed firmware version falls within the affected ranges (1.8.1 or lower for Encoder/Decoder, 1.11.0 or lower for Decoder Software, 1.23.7 or lower for SP/ISP).
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 dataDisable the telnet service if not required, or upgrade to a patched firmware version if available; otherwise implement network access controls to restrict telnet access to trusted IPs.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-4747 — 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-2007-4747 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