# CVE-2022-32549: log injection in Sling logging

> Attackers can inject fake entries into Apache Sling logs to corrupt files and hide malicious activity, requiring an upgrade to patched versions.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 22 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qmx3-m648-hr74

## What is CVE-2022-32549?

CVE-2022-32549 is a medium-severity vulnerability in Apache Sling, published on 22 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache Sling Commons Log <= 5.4.0 and Apache Sling API <= 2.25.0 are vulnerable to log injection. The ability to forge logs may allow an attacker to cover tracks by injecting fake logs and potentially corrupt log files.

Weakness: CWE-116 (Improper Encoding or Escaping of Output), CWE-117 (Improper Output Neutralization for Logs)

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

4 open source packages ship an affected version, including org.apache.sling:org.apache.sling.api and org.apache.sling:org.apache.sling.commons.log. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.sling:org.apache.sling.api` | Maven | All versions to 2.25.0 | None |
| `org.apache.sling:org.apache.sling.api` | Maven | All versions to 2.25.0 | None |
| `org.apache.sling:org.apache.sling.commons.log` | Maven | All versions to 5.4.0 | None |
| `org.apache.sling:org.apache.sling.commons.log` | Maven | All versions to 5.4.0 | None |

Products: Apache Sling Api, Apache Sling Commons Log.

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

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

## Is CVE-2022-32549 being exploited?

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

## Other vulnerabilities in Apache Sling

- [CVE-2015-2944](https://insights.sbomify.com/CVE-2015-2944/): Improper Neutralization of Input During Web Page Generation in Apache Sling (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-32549 is a medium-severity vulnerability in Apache Sling, published on 22 Jun 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-32549 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.sling:org.apache.sling.api (Maven): affected all versions up to 2.25.0; no fix listed
- org.apache.sling:org.apache.sling.api (Maven): affected all versions up to 2.25.0; no fix listed
- org.apache.sling:org.apache.sling.commons.log (Maven): affected all versions up to 5.4.0; no fix listed
- org.apache.sling:org.apache.sling.commons.log (Maven): affected all versions up to 5.4.0; no fix listed

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

## Sources

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

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