# CVE-2007-4747: Auth bypass in n/a

> Remote attackers can perform administrative actions on Cisco Video Surveillance IP Gateway devices without authentication due to missing access controls.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-876p-mjq3-fwgx

## What is CVE-2007-4747?

CVE-2007-4747 is a critical authentication bypass vulnerability in n/a, published on 6 Sep 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2007-4747?

It affects 3 products.


Products: Cisco Video Surveillance Ip Gateway Encoder Decoder, Cisco Video Surveillance Sp Isp, Cisco Video Surveillance Sp Isp Decoder Software.

## How do I fix CVE-2007-4747?

No fix has been published for CVE-2007-4747 yet. Limit exposure of the affected software until one is available.

## Is CVE-2007-4747 being exploited?

There is no known exploitation of CVE-2007-4747 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2007-4746](https://insights.sbomify.com/CVE-2007-4746/): Hardcoded credentials in n/a (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4747 and fix it if it is affected.

What it is: CVE-2007-4747 is a critical authentication bypass vulnerability in n/a, published on 6 Sep 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-4747 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2007-4747/ (Markdown: https://insights.sbomify.com/CVE-2007-4747/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2007-4747
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-4747
- OSV: https://osv.dev/vulnerability/CVE-2007-4747

---
From sbomify Insights: https://insights.sbomify.com/CVE-2007-4747/
Summaries are generated and may contain mistakes; the official description above is the record.