# CVE-2018-1280: SQL injection in Greenplum Command Center

> Unauthenticated attackers can exploit blind SQL injection in Greenplum Command Center to disclose sensitive database contents.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xw2x-258j-w7p8

## What is CVE-2018-1280?

CVE-2018-1280 is a high-severity SQL injection vulnerability in Pivotal Greenplum Command Center, published on 11 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pivotal Greenplum Command Center versions 2.x prior to 2.5.1 contains a blind SQL injection vulnerability. An unauthenticated user can perform a SQL injection in the command center which results in disclosure of database contents.

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

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

It affects 1 product.


Products: Pivotal Software Greenplum Command Center.

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

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

## Is CVE-2018-1280 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1280 is a high-severity SQL injection vulnerability in Pivotal Greenplum Command Center, published on 11 May 2018. 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-2018-1280 in the wild and no public exploit code.

Affected product: Pivotal Greenplum Command Center. 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-1280/ (Markdown: https://insights.sbomify.com/CVE-2018-1280/index.md)
```

## Sources

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

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