# CVE-2024-12989: WISI Tangram GT31 HTTP Request server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the WISI Tangram GT31 HTTP request handler to access internal resources.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Dec 2024
- **Updated:** 27 Dec 2024
- **Also known as:** GHSA-67qp-qff2-ggpp

## What is CVE-2024-12989?

CVE-2024-12989 is a medium-severity server-side request forgery vulnerability in WISI Tangram GT31, published on 27 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in WISI Tangram GT31 up to 20241214 and classified as problematic. Affected by this issue is some unknown functionality of the component HTTP Request Handler. The manipulation leads to server-side request forgery. The attack may be launched remotely. The vendor was contacted early about this disclosure but did not respond in any way.

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

## Which versions are affected by CVE-2024-12989?


## How do I fix CVE-2024-12989?

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

## Is CVE-2024-12989 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12989 and fix it if it is affected.

What it is: CVE-2024-12989 is a medium-severity server-side request forgery vulnerability in WISI Tangram GT31, published on 27 Dec 2024. 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-2024-12989 in the wild and no public exploit code.

Affected product: WISI Tangram GT31. 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-2024-12989/ (Markdown: https://insights.sbomify.com/CVE-2024-12989/index.md)
```

## Sources

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

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