ALBA-2019:3504 bacula bug fix and enhancement update
Not scored
Published
Check this codebase for ALBA-2019:3504 and fix it if it is affected.
What it is: ALBA-2019:3504 is an other vulnerability in bacula-client, published on 5 Nov 2019.
Exploitation: There is no known exploitation of ALBA-2019:3504 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: bacula-client. 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-2019-3504/ (Markdown: https://insights.sbomify.com/ALBA-2019-3504/index.md)
An unspecified flaw in the AlmaLinux Bacula backup package has been fixed; 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-2019:3504?
ALBA-2019:3504 is an other vulnerability in bacula-client, published on 5 Nov 2019.
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-2019:3504?
An affected version is exposed as installed. No special setting or call is needed.
Linux distribution packages (8)
bacula-client AlmaLinux:8 | All versions | 9.0.6-6.el8 |
bacula-common AlmaLinux:8 | All versions | 9.0.6-6.el8 |
bacula-console AlmaLinux:8 | All versions | 9.0.6-6.el8 |
bacula-director AlmaLinux:8 | All versions | 9.0.6-6.el8 |
bacula-libs AlmaLinux:8 | All versions | 9.0.6-6.el8 |
bacula-libs-sql AlmaLinux:8 | All versions | 9.0.6-6.el8 |
bacula-logwatch AlmaLinux:8 | All versions | 9.0.6-6.el8 |
bacula-storage AlmaLinux:8 | All versions | 9.0.6-6.el8 |
How do I fix ALBA-2019:3504?
Upgrade to a fixed version.
Upgrade to the fixed version. More about Other.
Is ALBA-2019:3504 being exploited?
There is no known exploitation of ALBA-2019:3504 in the wild and no public exploit code.