# CVE-2017-9246: New Relic .NET Agent contains SQL Injection

> The New Relic .NET Agent fails to escape quotes in SQL queries, allowing attackers to inject malicious SQL code when the Slow Queries feature is enabled.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2rvx-cvfc-mcp2

## What is CVE-2017-9246?

CVE-2017-9246 is a critical SQL injection vulnerability in n/a, published on 13 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

New Relic .NET Agent before 6.3.123.0 adds SQL injection flaws to safe applications via vectors involving failure to escape quotes during use of the Slow Queries feature, as demonstrated by a mishandled quote in a VALUES clause of an INSERT statement, after bypassing a SET SHOWPLAN_ALL ON protection mechanism.

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

## Which versions are affected by CVE-2017-9246?

2 open source packages ship an affected version, including NewRelic.Agent. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `NewRelic.Agent` | NuGet | All versions | 6.3.123.0 |
| `NewRelic.Agent` | NuGet | All versions | 6.3.123.0 |

Products: Newrelic .Net Agent.

## How do I fix CVE-2017-9246?

Upgrade NewRelic.Agent to 6.3.123.0 or later.

## Is CVE-2017-9246 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9246 and fix it if it is affected.

What it is: CVE-2017-9246 is a critical SQL injection vulnerability in n/a, published on 13 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9246 in the wild and no public exploit code.

Affected packages and fixed versions:
- NewRelic.Agent (NuGet): affected all versions; fixed in 6.3.123.0
- NewRelic.Agent (NuGet): affected all versions; fixed in 6.3.123.0

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

## Sources

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

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