# CVE-2018-7107: SQL injection in HPE Device Entitlement Gateway (DEG)

> Remote attackers can exploit SQL injection in HPE Device Entitlement Gateway to execute code and escalate privileges.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6gq3-77jq-hrr5

## What is CVE-2018-7107?

CVE-2018-7107 is a high-severity SQL injection vulnerability in Hewlett Packard Enterprise HPE Device Entitlement Gateway (DEG), published on 27 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A potential security vulnerability has been identified in HPE Device Entitlement Gateway (DEG) v3.2.4, v3.3 and v3.3.1. The vulnerability could be remotely exploited to allow local SQL injection and elevation of privilege.

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

## Which versions are affected by CVE-2018-7107?

It affects 1 product.


Products: Hpe Device Entitlement Gateway.

## How do I fix CVE-2018-7107?

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

## Is CVE-2018-7107 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7107 and fix it if it is affected.

What it is: CVE-2018-7107 is a high-severity SQL injection vulnerability in Hewlett Packard Enterprise HPE Device Entitlement Gateway (DEG), published on 27 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-7107 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise HPE Device Entitlement Gateway (DEG). 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-2018-7107/ (Markdown: https://insights.sbomify.com/CVE-2018-7107/index.md)
```

## Sources

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

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