Security readout for executives and security teams
Plain-English summary
License to Kill has a SQL injection flaw in models/injury.rb tied to handling the name argument. A logged-in attacker with adjacent access could potentially read or change limited data or disrupt availability. Public sources name a patch commit, but affected versions and deployment prevalence are not specified.
Executive priority
Handle as a moderate-priority remediation. The flaw can affect confidentiality, integrity, and availability, but public evidence suggests constrained access requirements and no confirmed active exploitation. Escalate priority if this code protects sensitive data or is reachable from untrusted adjacent networks.
Technical view
CVE-2014-125037 is CWE-89 SQL injection in License to Kill. The CVSS 3.1 vector is AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, score 5.5. The vulnerable component is models/injury.rb, with manipulation of name leading to SQL injection. The referenced fix is commit cd11cf174f361c98e9b1b4c281aa7b77f46b5078.
Likely exposure
Exposure is limited to organizations running License to Kill code that includes the vulnerable models/injury.rb behavior. Sources do not provide affected version ranges, CPEs, package identifiers, or evidence of broad ecosystem deployment.
Exploitation context
No source in the bundle indicates active exploitation, and the CVE is not listed as KEV. The scoring indicates exploitation requires adjacent access and low privileges, with no user interaction. Public details identify the vulnerable argument and patch but do not establish exploit availability.
Researcher notes
Evidence is sparse: vendor is listed as n/a, versions are n/a, and CPEs are absent. Treat affected-surface analysis as code-based rather than product-version-based. Do not infer exploit maturity from the vulnerability description alone.
Mitigation direction
- Apply the referenced upstream patch commit after normal change testing.
- Check project guidance for any newer fixed revision or release.
- Prioritize systems where License to Kill has sensitive database access.
- Restrict access to affected application paths where operationally feasible.
- Use least-privilege database permissions to reduce impact.
Validation and detection
- Inventory whether License to Kill is deployed or vendored internally.
- Check for models/injury.rb and pre-patch handling of the name argument.
- Confirm commit cd11cf174f361c98e9b1b4c281aa7b77f46b5078 or equivalent fix is present.
- Review application and database logs for suspicious name-parameter errors.
- Validate fixes in staging without using offensive payloads.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2014-125037 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.13.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://vuldb.com/?id.217191CVE reference · vdb-entry, technical-description
- https://vuldb.com/?ctiid.217191CVE reference · signature, permissions-required
- https://github.com/elizabrock/license-to-kill/commit/cd11cf174f361c98e9b1b4c281aa7b77f46b5078CVE reference · patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
