# CVE-2020-25185: Memory corruption in IP150

> A logged-in user can trigger buffer overflows to remotely execute arbitrary code on the IP150 gateway.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xrmc-6wqq-99wc

## What is CVE-2020-25185?

CVE-2020-25185 is a high-severity memory corruption vulnerability in IP150, published on 21 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The affected product is vulnerable to five post-authentication buffer overflows, which may allow a logged in user to remotely execute arbitrary code on the IP150 (firmware versions 5.02.09).

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2020-25185?

It affects 1 product.


Products: Paradox Ip150 Firmware.

## How do I fix CVE-2020-25185?

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

## Is CVE-2020-25185 being exploited?

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

## Other vulnerabilities in IP150

- [CVE-2020-25189](https://insights.sbomify.com/CVE-2020-25189/): Memory corruption in IP150 (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25185 and fix it if it is affected.

What it is: CVE-2020-25185 is a high-severity memory corruption vulnerability in IP150, published on 21 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-25185 in the wild and no public exploit code.

Affected product: IP150. 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-2020-25185/ (Markdown: https://insights.sbomify.com/CVE-2020-25185/index.md)
```

## Sources

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

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