CVE-2024-12989
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA Server-Side Request Forgery (SSRF) vulnerability exists in the HTTP Request Handler component of WISI Tangram GT31 devices. An attacker can manipulate HTTP requests to cause the server to make unintended requests to internal network resources or external systems, potentially bypassing network boundaries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is WISI Tangram GT31Access the device administrative interface or check the device firmware/system information to verify the exact model number matches 'Tangram GT31'Affected if The device is not a WISI Tangram GT31 model, then this specific CVE does not apply
-
Locate HTTP Request Handler configurationNavigate to the device web interface or configuration files and search for settings related to 'HTTP Request Handler', 'HTTP Client', or 'Outbound HTTP' functionalityAffected if No HTTP Request Handler feature exists in the configuration, then the device may not be vulnerable to this specific attack vector
-
Verify HTTP Request Handler is enabledCheck the device configuration for the HTTP Request Handler feature and confirm it is set to 'enabled' or 'active' rather than disabledAffected if The HTTP Request Handler is explicitly disabled in the device configuration, the SSRF attack surface may not be present
-
Review outbound HTTP request configurationsExamine the HTTP Request Handler settings for any configured target URLs, IP addresses, or hostnames that the device is authorized to requestAffected if The handler allows arbitrary or user-controllable URL parameters that could be manipulated to trigger SSRF
-
Inspect network traffic logs for unexpected HTTP requestsReview device logs, firewall logs, or network monitoring data for HTTP requests originating from the device to internal IP ranges (such as 10.x.x.x, 192.168.x.x, 127.x.x.x) or unexpected external destinationsAffected if The device has made or attempted HTTP requests to internal network resources or unauthorized external hosts that were not explicitly configured
A user is affected if they operate a WISI Tangram GT31 device with the HTTP Request Handler feature enabled and accessible, allowing an attacker to manipulate HTTP requests for unauthorized network access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince no vendor patch is available, implement network segmentation and firewall rules to restrict outbound HTTP requests from the device. If possible, disable or restrict the HTTP Request Handler functionality through device configuration.
- Consultation3.0 h
- Implementation5.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12989 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-12989 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data