ALEA-2022:1963 new module: log4j:2
Not scored
Published
Check this codebase for ALEA-2022:1963 and fix it if it is affected.
What it is: ALEA-2022:1963 is a vulnerability in disruptor, published on 10 May 2022.
Exploitation: There is no known exploitation of ALEA-2022:1963 in the wild and no public exploit code.
Affected product: disruptor. 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/ALEA-2022-1963/ (Markdown: https://insights.sbomify.com/ALEA-2022-1963/index.md)
This update adds the log4j:2 module to AlmaLinux, providing the library for use but not describing a specific vulnerability or attack vector.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- Available
What is ALEA-2022:1963?
ALEA-2022:1963 is a vulnerability in disruptor, published on 10 May 2022.
Official description
This enhancement update adds the log4j:2 module to AlmaLinux (BZ#1937468)
For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.
Which versions are affected by ALEA-2022:1963?
Linux distribution packages (10)
disruptor AlmaLinux:8 | All versions | 3.4.4-2.module_el8.6.0+2875+d267bdfe |
disruptor AlmaLinux:8 | All versions | 3.4.4-2.module_el8.6.0+2885+57fd4498 |
jctools AlmaLinux:8 | All versions | 3.3.0-3.module_el8.6.0+2875+d267bdfe |
jctools AlmaLinux:8 | All versions | 3.3.0-3.module_el8.6.0+2885+57fd4498 |
log4j AlmaLinux:8 | All versions | 2.17.1-4.module_el8.6.0+2875+d267bdfe |
log4j AlmaLinux:8 | All versions | 2.17.1-4.module_el8.6.0+2885+57fd4498 |
log4j-jcl AlmaLinux:8 | All versions | 2.17.1-4.module_el8.6.0+2875+d267bdfe |
log4j-jcl AlmaLinux:8 | All versions | 2.17.1-4.module_el8.6.0+2885+57fd4498 |
log4j-slf4j AlmaLinux:8 | All versions | 2.17.1-4.module_el8.6.0+2875+d267bdfe |
log4j-slf4j AlmaLinux:8 | All versions | 2.17.1-4.module_el8.6.0+2885+57fd4498 |
How do I fix ALEA-2022:1963?
Upgrade to a fixed version.
Is ALEA-2022:1963 being exploited?
There is no known exploitation of ALEA-2022:1963 in the wild and no public exploit code.