How severe is CVE-2014-125064?

CVE-2014-125064 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2014-125064?

CVE-2014-125064 affects the following packages: github.com/elgs/gosqljson (Go). Ecosystems affected: Go.

How do I fix CVE-2014-125064?

Update github.com/elgs/gosqljson to 0.0.0-20220916234230-750f26ee23c7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-125064 is resolved across your whole dependency graph.

How do I detect CVE-2014-125064 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/elgs/gosqljson, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-125064 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2014-125064?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-125064 can be triaged on real exposure rather than presence alone.

Is CVE-2014-125064 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-125064 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2014-125064 published, and has it been updated?

CVE-2014-125064 was published on January 7, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

CRITICAL severity

CVE-2014-125064 — gosqljson

CRITICALFix: elgs/gosqljson@2740b33

CVE-2014-125064 is a critical-severity (CVSS 9.8) vulnerability in github.com/elgs/gosqljson. A fix is available for github.com/elgs/gosqljson — see the affected versions and patch details below.

gosqljson SQL Injection vulnerability

Also known asGO-2023-1494

Published

Jan 7, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/elgs/gosqljson

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

A vulnerability, which was classified as critical, has been found in elgs gosqljson. This issue affects the function QueryDbToArray/QueryDbToMap/ExecDb of the file gosqljson.go. The manipulation of the argument sqlStatement leads to sql injection. The name of the patch is 2740b331546cb88eb61771df4c07d389e9f0363a. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-217631.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/elgs/gosqljson`	all versions	0.0.0-20220916234230-750f26ee23c7`go get github.com/elgs/gosqljson@v0.0.0-20220916234230-750f26ee23c7`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/elgs/gosqljson, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/elgs/gosqljson to 0.0.0-20220916234230-750f26ee23c7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-125064 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-125064 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2014-125064. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A vulnerability, which was classified as critical, has been found in elgs gosqljson. This issue affects the function `QueryDbToArray/QueryDbToMap/ExecDb` of the file `gosqljson.go`. The manipulation of the argument sqlStatement leads to sql injection. The name of the patch is 2740b331546cb88eb61771df4c07d389e9f0363a. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-217631.

O3 Security · Impact-Aware SCA

Is CVE-2014-125064 in your dependencies?

O3 Security finds CVE-2014-125064 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works