# CVE-2014-125037: License to Kill injury.rb sql injection

> SQL injection in License to Kill allows attackers to manipulate database queries via the injury model, requiring a patch for mitigation.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jan 2023
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-whhc-cv9p-pgmj

## What is CVE-2014-125037?

CVE-2014-125037 is a medium-severity SQL injection vulnerability in License to Kill, published on 2 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in License to Kill. This affects an unknown part of the file models/injury.rb. The manipulation of the argument name leads to sql injection. The patch is named cd11cf174f361c98e9b1b4c281aa7b77f46b5078. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-217191.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2014-125037?

It affects 1 product.


Products: License to Kill Project License to Kill.

## How do I fix CVE-2014-125037?

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

## Is CVE-2014-125037 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-125037 and fix it if it is affected.

What it is: CVE-2014-125037 is a medium-severity SQL injection vulnerability in License to Kill, published on 2 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-125037 in the wild and no public exploit code.

Affected product: License to Kill. 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-2014-125037/ (Markdown: https://insights.sbomify.com/CVE-2014-125037/index.md)
```

## Sources

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

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