ALBA-2022:1815 389-ds:1.4 bug fix and enhancement update
Not scored
Published
Check this codebase for ALBA-2022:1815 and fix it if it is affected.
What it is: ALBA-2022:1815 is an other vulnerability in 389-ds-base, published on 10 May 2022.
Exploitation: There is no known exploitation of ALBA-2022:1815 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.
Affected product: 389-ds-base. 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-2022-1815/ (Markdown: https://insights.sbomify.com/ALBA-2022-1815/index.md)
An unspecified bug fix and enhancement update affects 389 Directory Server; AlmaLinux administrators should apply the update.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Harmful if only installed
- No
- Needs a specific call
- No
- Fix
- Available
What is ALBA-2022:1815?
ALBA-2022:1815 is an other vulnerability in 389-ds-base, published on 10 May 2022.
Official description
For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.
Which versions are affected by ALBA-2022:1815?
An affected version is exposed as installed. No special setting or call is needed.
Linux distribution packages (6)
389-ds-base AlmaLinux:8 | All versions | 1.4.3.28-6.module_el8.6.0+2734+1efaf02b |
389-ds-base-devel AlmaLinux:8 | All versions | 1.4.3.28-6.module_el8.6.0+2734+1efaf02b |
389-ds-base-legacy-tools AlmaLinux:8 | All versions | 1.4.3.28-6.module_el8.6.0+2734+1efaf02b |
389-ds-base-libs AlmaLinux:8 | All versions | 1.4.3.28-6.module_el8.6.0+2734+1efaf02b |
389-ds-base-snmp AlmaLinux:8 | All versions | 1.4.3.28-6.module_el8.6.0+2734+1efaf02b |
python3-lib389 AlmaLinux:8 | All versions | 1.4.3.28-6.module_el8.6.0+2734+1efaf02b |
How do I fix ALBA-2022:1815?
Upgrade to a fixed version.
Upgrade to the fixed version. More about Other.
Is ALBA-2022:1815 being exploited?
There is no known exploitation of ALBA-2022:1815 in the wild and no public exploit code.