# Log Injection in Apache Sling Commons Log and Apache Sling API

Advisory record · `GHSA-qmx3-m648-hr74`

- **Identifiers:** `GHSA-qmx3-m648-hr74` · `CVE-2022-32549`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-116](https://cwe.mitre.org/data/definitions/116.html) · [CWE-117](https://cwe.mitre.org/data/definitions/117.html)
- **Tags:** [Other injection](https://agentprime.io/advisories/tag/injection.md) · [CWE-116](https://agentprime.io/advisories/tag/cwe-116.md)
- **Published:** 23 Jun 2022
- **Updated:** 8 Nov 2023
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 Jun 2022, 00:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.sling:org.apache.sling.commons.log` (Maven): affected `<=5.4.0`; no fixed version yet
- `org.apache.sling:org.apache.sling.api` (Maven): affected `<=2.25.0`; no fixed version yet

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.024, the 84th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 23 Jun 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-qmx3-m648-hr74](https://github.com/advisories/GHSA-qmx3-m648-hr74)
- [OSV: GHSA-qmx3-m648-hr74](https://osv.dev/vulnerability/GHSA-qmx3-m648-hr74)
- <https://nvd.nist.gov/vuln/detail/CVE-2022-32549>
- <https://lists.apache.org/thread/7z6h3806mwcov5kx6l96pq839sn0po1v>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-qmx3-m648-hr74>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-qmx3-m648-hr74/>. Everything for agents: <https://agentprime.io/llms.txt>.