# CVE-2022-0552: Other in origin-aggregated-logging/elasticsearch

> Incomplete fix in OpenShift Logging container left vulnerable Netty library, requiring patching to address residual security flaws.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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 Apr 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-4r7g-fj95-jwpc

## What is CVE-2022-0552?

CVE-2022-0552 is a medium-severity vulnerability in origin-aggregated-logging/elasticsearch, published on 11 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in the original fix for the netty-codec-http CVE-2021-21409, where the OpenShift Logging openshift-logging/elasticsearch6-rhel8 container was incomplete. The vulnerable netty-codec-http maven package was not removed from the image content. This flaw affects origin-aggregated-logging versions 3.11.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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

It affects 1 product.


Products: Redhat Origin-Aggregated-Logging.

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

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

## Is CVE-2022-0552 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0552 is a medium-severity vulnerability in origin-aggregated-logging/elasticsearch, published on 11 Apr 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-0552 in the wild and no public exploit code.

Affected product: origin-aggregated-logging/elasticsearch. 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-0552/ (Markdown: https://insights.sbomify.com/CVE-2022-0552/index.md)
```

## Sources

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

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