ALBA-2020:4857 idm:DL1 bug fix update
Not scored
Published
Check this codebase for ALBA-2020:4857 and fix it if it is affected.
What it is: ALBA-2020:4857 is a vulnerability in custodia, published on 4 Nov 2020.
Exploitation: There is no known exploitation of ALBA-2020:4857 in the wild and no public exploit code.
Affected product: custodia. 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/ALBA-2020-4857/ (Markdown: https://insights.sbomify.com/ALBA-2020-4857/index.md)
A bug fix update for AlmaLinux Identity Management addresses an issue where nsslapd-db-locks patching was not working correctly.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- Available
What is ALBA-2020:4857?
ALBA-2020:4857 is a vulnerability in custodia, published on 4 Nov 2020.
Official description
AlmaLinux Identity Management (IdM) is a centralized authentication, identity management, and authorization solution for both traditional and cloud-based enterprise environments.
Bug Fix(es):
- nsslapd-db-locks patching no longer works (BZ#1882472)
Which versions are affected by ALBA-2020:4857?
Linux distribution packages (21)
custodia AlmaLinux:8 | All versions | 0.6.0-3.module_el8.5.0+2603+92118e57 |
custodia AlmaLinux:8 | All versions | 0.6.0-3.module_el8.6.0+2881+2f24dc92 |
python3-custodia AlmaLinux:8 | All versions | 0.6.0-3.module_el8.5.0+2603+92118e57 |
python3-custodia AlmaLinux:8 | All versions | 0.6.0-3.module_el8.6.0+2881+2f24dc92 |
python3-jwcrypto AlmaLinux:8 | All versions | 0.5.0-1.module_el8.5.0+2603+92118e57 |
python3-jwcrypto AlmaLinux:8 | All versions | 0.5.0-1.module_el8.6.0+2737+7e73ea90 |
python3-jwcrypto AlmaLinux:8 | All versions | 0.5.0-1.module_el8.6.0+2881+2f24dc92 |
python3-kdcproxy AlmaLinux:8 | All versions | 0.4-5.module_el8.5.0+2603+92118e57 |
python3-kdcproxy AlmaLinux:8 | All versions | 0.4-5.module_el8.6.0+2881+2f24dc92 |
python3-pyusb AlmaLinux:8 | All versions | 1.0.0-9.module_el8.5.0+2603+92118e57 |
python3-pyusb AlmaLinux:8 | All versions | 1.0.0-9.module_el8.6.0+2737+7e73ea90 |
python3-pyusb AlmaLinux:8 | All versions | 1.0.0-9.module_el8.6.0+2881+2f24dc92 |
python3-qrcode AlmaLinux:8 | All versions | 5.1-12.module_el8.5.0+2603+92118e57 |
python3-qrcode AlmaLinux:8 | All versions | 5.1-12.module_el8.6.0+2737+7e73ea90 |
python3-qrcode AlmaLinux:8 | All versions | 5.1-12.module_el8.6.0+2881+2f24dc92 |
python3-qrcode-core AlmaLinux:8 | All versions | 5.1-12.module_el8.5.0+2603+92118e57 |
python3-qrcode-core AlmaLinux:8 | All versions | 5.1-12.module_el8.6.0+2737+7e73ea90 |
python3-qrcode-core AlmaLinux:8 | All versions | 5.1-12.module_el8.6.0+2881+2f24dc92 |
python3-yubico AlmaLinux:8 | All versions | 1.3.2-9.module_el8.5.0+2603+92118e57 |
python3-yubico AlmaLinux:8 | All versions | 1.3.2-9.module_el8.6.0+2737+7e73ea90 |
python3-yubico AlmaLinux:8 | All versions | 1.3.2-9.module_el8.6.0+2881+2f24dc92 |
How do I fix ALBA-2020:4857?
Apply the vendor's patch.
Is ALBA-2020:4857 being exploited?
There is no known exploitation of ALBA-2020:4857 in the wild and no public exploit code.