# CVE-2019-12968: A vulnerability was found in the Sonic Robo Blast 2 (SRB2) plugin (EP_Versions 9 to 11 inclusive) distributed with Doomseeker 1.1 and 1.2.


- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8fw7-x954-66rg

## What is CVE-2019-12968?

CVE-2019-12968 is a medium-severity vulnerability in n/a, published on 26 Jun 2019. 

### Official description

A vulnerability was found in the Sonic Robo Blast 2 (SRB2) plugin (EP_Versions 9 to 11 inclusive) distributed with Doomseeker 1.1 and 1.2. Affected plugin versions did not discard IP packets with an unnaturally long response length from a Sonic Robo Blast 2 master server, allowing a remote attacker to cause a potential crash / denial of service in Doomseeker. The issue has been remediated in the Doomseeker 1.3 release with source code patches to the SRB2 plugin.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2019-12968?

It affects 1 product.


Products: Drdteam Doomseeker.

## How do I fix CVE-2019-12968?

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

## Is CVE-2019-12968 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12968 and fix it if it is affected.

What it is: CVE-2019-12968 is a medium-severity vulnerability in n/a, published on 26 Jun 2019. 
Exploitation: There is no known exploitation of CVE-2019-12968 in the wild and no public exploit code.

Affected product: n/a. 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-2019-12968/ (Markdown: https://insights.sbomify.com/CVE-2019-12968/index.md)
```

## Sources

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

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