# CVE-2005-1552: Missing authorization in n/a

> Remote attackers can access protected JPEG images without authentication in GeoVision surveillance systems configured to generate images.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6rhq-4f3p-6vm5

## What is CVE-2005-1552?

CVE-2005-1552 is a medium-severity missing authorization vulnerability in n/a, published on 14 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GeoVision Digital Video Surveillance System 6.04, 6.1 and 7.0, when set to create JPEG images, does not properly protect an image even when a password and username is assigned, which may allow remote attackers to gain sensitive information via a direct request to the image.

## Which versions are affected by CVE-2005-1552?

It affects 1 product.


Products: Geovision Digital Surveillance System.

## How do I fix CVE-2005-1552?

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

## Is CVE-2005-1552 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1552 exists.

Public exploit code:

- GeoVision Digital Surveillance System 6.0 4/6.1 - Unauthorized '.JPEG' Image Access (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-1553](https://insights.sbomify.com/CVE-2005-1553/): Weak cryptography in n/a (high 7.5)
- [CVE-2009-5087](https://insights.sbomify.com/CVE-2009-5087/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1552 and fix it if it is affected.

What it is: CVE-2005-1552 is a medium-severity missing authorization vulnerability in n/a, published on 14 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1552 exists.

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-2005-1552/ (Markdown: https://insights.sbomify.com/CVE-2005-1552/index.md)
```

## Sources

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

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