# CVE-2014-125079: agy pontifex.http Http.coffee sql injection


- **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
- **Fix available:** No
- **Published:** 15 Jan 2023
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-frmg-377c-8r42

## What is CVE-2014-125079?

CVE-2014-125079 is a medium-severity vulnerability in agy pontifex.http, published on 15 Jan 2023. 

### Official description

A vulnerability was found in agy pontifex.http. It has been declared as critical. This vulnerability affects unknown code of the file lib/Http.coffee. The manipulation leads to sql injection. Upgrading to version 0.1.0 is able to address this issue. The name of the patch is e52a758f96861dcef2dabfecb9da191bb2e07761. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-218356.

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

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

It affects 1 product.


Products: Pontifex.http Project Pontifex.http.

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

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

## Is CVE-2014-125079 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-125079 is a medium-severity vulnerability in agy pontifex.http, published on 15 Jan 2023. 
Exploitation: There is no known exploitation of CVE-2014-125079 in the wild and no public exploit code.

Affected product: agy pontifex.http. 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-125079/ (Markdown: https://insights.sbomify.com/CVE-2014-125079/index.md)
```

## Sources

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

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