# CVE-2022-28623: SQL injection in HPE IceWall SSO

> Remote attackers can exploit SQL injection in HPE IceWall SSO certd to read or modify unauthorized data.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** No
- **Published:** 8 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5533-fm9f-hg7j

## What is CVE-2022-28623?

CVE-2022-28623 is a critical SQL injection vulnerability in HPE IceWall SSO, published on 8 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Security vulnerabilities in HPE IceWall SSO 10.0 certd could be exploited remotely to allow SQL injection or unauthorized data injection. HPE has provided the following updated modules to resolve these vulnerabilities. HPE IceWall SSO version 10.0 certd library Patch 9 for RHEL and HPE IceWall SSO version 10.0 certd library Patch 9 for HP-UX.

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

## Which versions are affected by CVE-2022-28623?

It affects 1 product.


Products: Hpe Icewall Sso Certd.

## How do I fix CVE-2022-28623?

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

## Is CVE-2022-28623 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-28623 and fix it if it is affected.

What it is: CVE-2022-28623 is a critical SQL injection vulnerability in HPE IceWall SSO, published on 8 Jul 2022. 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-2022-28623 in the wild and no public exploit code.

Affected product: HPE IceWall SSO. 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-2022-28623/ (Markdown: https://insights.sbomify.com/CVE-2022-28623/index.md)
```

## Sources

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

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