SUSE-SU-2018:0510-1 Security update for libdb-4_8
Not scored
Published
Check this codebase for SUSE-SU-2018:0510-1 and fix it if it is affected.
What it is: SUSE-SU-2018:0510-1 is a vulnerability in libdb-4_8, published on 21 Feb 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2018:0510-1 in the wild and no public exploit code.
Affected product: libdb-4_8. 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/SUSE-SU-2018-0510-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2018-0510-1/index.md)
Local attackers can exploit symlink attacks in setuid/setgid applications using libdb-4_8 to read sensitive information via DB_CONFIG.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is SUSE-SU-2018:0510-1?
SUSE-SU-2018:0510-1 is a vulnerability in libdb-4_8, published on 21 Feb 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
This update for libdb-4_8 fixes the following issues:
- A DB_CONFIG file in the current working directory allowed local users to obtain sensitive information via a symlink attack involving a setgid or setuid application using libdb-4_8. (bsc#1043886)
Which versions are affected by SUSE-SU-2018:0510-1?
Linux distribution packages (9)
libdb-4_8 SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 4.8.30-29.6 |
libdb-4_8 SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 4.8.30-29.6 |
libdb-4_8 SUSE:Linux Enterprise Server 12 SP2 | All versions | 4.8.30-29.6 |
libdb-4_8 SUSE:Linux Enterprise Server 12 SP3 | All versions | 4.8.30-29.6 |
libdb-4_8 SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 4.8.30-29.6 |
libdb-4_8 SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 4.8.30-29.6 |
libdb-4_8 SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 4.8.30-29.6 |
libdb-4_8 SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 4.8.30-29.6 |
libdb-4_8 SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 4.8.30-29.6 |
How do I fix SUSE-SU-2018:0510-1?
Apply the vendor's patch.
Is SUSE-SU-2018:0510-1 being exploited?
There is no known exploitation of SUSE-SU-2018:0510-1 in the wild and no public exploit code.