# CVE-2022-2025: Grandstream GSD3710 Stack-based Buffer Overflow

> An authenticated attacker can execute arbitrary code with full access via a stack-based buffer overflow in the Grandstream GSD3710.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2022
- **Updated:** 22 May 2025
- **Also known as:** GHSA-3qjj-8gwh-qxvc

## What is CVE-2022-2025?

CVE-2022-2025 is a critical memory corruption vulnerability in Grandstream GSD3710, published on 23 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

an attacker with knowledge of user/pass of Grandstream GSD3710 in its 1.0.11.13 version, could overflow the stack since it doesn't check the param length before use the strcopy instruction. The explotation of this vulnerability may lead an attacker to execute a shell with full access.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2022-2025?

It affects 1 product.


Products: Grandstream Gds3710 Firmware.

## How do I fix CVE-2022-2025?

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

## Is CVE-2022-2025 being exploited?

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

Public exploit code:

- Grandstream GSD3710 1.0.11.13 - Stack Overflow (exploitdb)

## Other vulnerabilities in Grandstream GSD3710

- [CVE-2022-2070](https://insights.sbomify.com/CVE-2022-2070/): Grandstream GSD3710 Stack-based Buffer Overflow (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2025 and fix it if it is affected.

What it is: CVE-2022-2025 is a critical memory corruption vulnerability in Grandstream GSD3710, published on 23 Sep 2022. 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-2022-2025 in the wild and no public exploit code.

Affected product: Grandstream GSD3710. 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-2022-2025/ (Markdown: https://insights.sbomify.com/CVE-2022-2025/index.md)
```

## Sources

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

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