CVE-2022-32549 json
log injection in Sling logging
published 4y ago modified 4mo ago also GHSA-qmx3-m648-hr74 , EUVD-2022-6134
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2022-32549 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-32549 updated cvss 5.3
Sling: log injection in Sling logging
-
Red Hat Integration Data Virtualisation Operator org.apache.sling org.apache.sling Red Hat Integration Service Registry org.apache.sling org.apache.sling Red Hat JBoss Data Grid 7 org.apache.sling org.apache.slingaffected: no fix planned “Out of support scope”
-
Red Hat Data Grid 8 org.apache.sling org.apache.sling Red Hat Fuse 7 org.apache.sling org.apache.sling Red Hat Integration Camel K 1 org.apache.sling org.apache.sling Red Hat JBoss Enterprise Application Platform 7 org.apache.sling org.apache.sling Red Hat JBoss Enterprise Application Platform Expansion Pack org.apache.sling org.apache.slingnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.45% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.sling:org.apache.sling.commons.log | <=5.4.0 |
no fix listed |
| maven | org.apache.sling:org.apache.sling.api | <=2.25.0 |
no fix listed |
Affected products
- Apache Software Foundation Apache Sling
Classification
References
-
lists.apache.org
/thread/7z6h3806mwcov5kx6l96pq839sn0po1v
web, mailing-list, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-32549
advisory
Sources
- CVE List CVE-2022-32549
- GitHub Advisory GHSA-qmx3-m648-hr74
- NVD CVE-2022-32549
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.