# CVE-2014-125064: gosqljson SQL Injection vulnerability


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 7 Jan 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-g7mw-9pf9-p2pm, GO-2023-1494

## What is CVE-2014-125064?

CVE-2014-125064 is a vulnerability in github.com/elgs/gosqljson, published on 7 Jan 2023. 

### Official description

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.

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

3 open source packages ship an affected version, including github.com/elgs/gosqljson.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/elgs/gosqljson` | Go | All versions | 0.0.0-20220916234230-750f26ee23c7 |
| `github.com/elgs/gosqljson` | Go | All versions | 0.0.0-20220916234230-750f26ee23c7 |
| `github.com/elgs/gosqljson` | Go | All versions | 0.0.0-20220916234230-750f26ee23c7 |

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

Upgrade github.com/elgs/gosqljson to 0.0.0-20220916234230-750f26ee23c7 or later.

## Is CVE-2014-125064 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-125064 is a vulnerability in github.com/elgs/gosqljson, published on 7 Jan 2023. 
Exploitation: There is no known exploitation of CVE-2014-125064 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/elgs/gosqljson (Go): affected all versions; fixed in 0.0.0-20220916234230-750f26ee23c7
- github.com/elgs/gosqljson (Go): affected all versions; fixed in 0.0.0-20220916234230-750f26ee23c7
- github.com/elgs/gosqljson (Go): affected all versions; fixed in 0.0.0-20220916234230-750f26ee23c7

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-125064/ (Markdown: https://insights.sbomify.com/CVE-2014-125064/index.md)
```

## Sources

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

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