# ALBA-2019:0987: mariadb:10.3 bug fix update

> A bug in MariaDB causes data corruption when altering columns used in primary keys, requiring an update to ensure data integrity.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 7 May 2019

## What is ALBA-2019:0987?

ALBA-2019:0987 is a vulnerability in Judy, published on 7 May 2019. 

### Official description

MariaDB is a multi-user, multi-threaded SQL database server that is binary compatible with MySQL. 

Bug Fix(es):

* Altering table's column used in primary key causes data corruption (BZ#1702602)

## Which versions are affected by ALBA-2019:0987?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Judy` | AlmaLinux:8 | All versions | 1.0.5-18.module_el8.5.0+2632+14ced695 |
| `Judy` | AlmaLinux:8 | All versions | 1.0.5-18.module_el8.6.0+2761+593e5e59 |
| `Judy` | AlmaLinux:8 | All versions | 1.0.5-18.module_el8.6.0+2867+72759d2f |

## How do I fix ALBA-2019:0987?

Upgrade to a fixed version.

## Is ALBA-2019:0987 being exploited?

There is no known exploitation of ALBA-2019:0987 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALBA-2019:0987 and fix it if it is affected.

What it is: ALBA-2019:0987 is a vulnerability in Judy, published on 7 May 2019. 
Exploitation: There is no known exploitation of ALBA-2019:0987 in the wild and no public exploit code.

Affected product: Judy. 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-0987/ (Markdown: https://insights.sbomify.com/ALBA-2019-0987/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2019:0987

---
From sbomify Insights: https://insights.sbomify.com/ALBA-2019-0987/
Summaries are generated and may contain mistakes; the official description above is the record.