# CVE-2018-7516: Server-side request forgery in Geutebrück G-Cam/EFD-2250 (part n° 5.02024) firmware and Topline TopFD-2125 (part n° 5.02820) firmware

> Attackers can exploit a server-side request forgery flaw in Geutebruck and Topline IP cameras to perform proxied network scans.

- **Severity:** High 7.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5758-75jc-f6ch

## What is CVE-2018-7516?

CVE-2018-7516 is a high-severity server-side request forgery vulnerability in Geutebrück G-Cam/EFD-2250 (part n° 5.02024) firmware and Topline TopFD-2125 (part n° 5.02820) firmware, published on 22 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A server-side request forgery vulnerability has been identified in Geutebruck G-Cam/EFD-2250 Version 1.12.0.4 and Topline TopFD-2125 Version 3.15.1 IP cameras, which could lead to proxied network scans.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2018-7516?

It affects 2 products.


Products: Geutebrueck G-Cam\/Efd-2250 Firmware, Geutebrueck Topfd-2125 Firmware.

## How do I fix CVE-2018-7516?

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

## Is CVE-2018-7516 being exploited?

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

## Other vulnerabilities in Geutebrück G-Cam/EFD-2250 (part n° 5.02024) firmware and Topline TopFD-2125 (part n° 5.02820) firmware

- [CVE-2018-7520](https://insights.sbomify.com/CVE-2018-7520/): Missing authorization in Geutebrück G-Cam/EFD-2250 (part n° 5.02024) firmware and Topline TopFD-2125 (part n° 5.02820) firmware (critical 9.8)
- [CVE-2018-7532](https://insights.sbomify.com/CVE-2018-7532/): Auth bypass in Geutebrück G-Cam/EFD-2250 (part n° 5.02024) firmware and Topline TopFD-2125 (part n° 5.02820) firmware (critical 9.8)
- [CVE-2018-7528](https://insights.sbomify.com/CVE-2018-7528/): SQL injection in Geutebrück G-Cam/EFD-2250 (part n° 5.02024) firmware and Topline TopFD-2125 (part n° 5.02820) firmware (critical 9.1)
- [CVE-2018-7524](https://insights.sbomify.com/CVE-2018-7524/): Cross-site request forgery in Geutebrück G-Cam/EFD-2250 (part n° 5.02024) firmware and Topline TopFD-2125 (part n° 5.02820) firmware (high 8.8)
- [CVE-2018-7512](https://insights.sbomify.com/CVE-2018-7512/): Cross-site scripting in Geutebrück G-Cam/EFD-2250 (part n° 5.02024) firmware and Topline TopFD-2125 (part n° 5.02820) firmware (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7516 and fix it if it is affected.

What it is: CVE-2018-7516 is a high-severity server-side request forgery vulnerability in Geutebrück G-Cam/EFD-2250 (part n° 5.02024) firmware and Topline TopFD-2125 (part n° 5.02820) firmware, published on 22 Mar 2018. 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-2018-7516 in the wild and no public exploit code.

Affected product: Geutebrück G-Cam/EFD-2250 (part n° 5.02024) firmware and Topline TopFD-2125 (part n° 5.02820) firmware. 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-2018-7516/ (Markdown: https://insights.sbomify.com/CVE-2018-7516/index.md)
```

## Sources

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

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