# ALBA-2022:1032: tzdata bug fix and enhancement update

> An update to tzdata fixes issues with reading corrupted time zone data, potentially preventing crashes or errors in time zone processing.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Mar 2022

## What is ALBA-2022:1032?

ALBA-2022:1032 is a vulnerability in tzdata, published on 23 Mar 2022. 

### Official description

The tzdata packages contain data files with rules for various time zones.

The tzdata packages have been updated to version 2022a, which addresses recent
time zone changes. Notably:

* In Palestine the daylight saving time (DST) starts on March 27, 2022, not on March 26.

* The zdump -v command now outputs better failure information.

* This update provides fixes for a code that read corrupted TZif data.

## Which versions are affected by ALBA-2022:1032?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tzdata` | AlmaLinux:8 | All versions | 2022a-1.el8 |
| `tzdata-java` | AlmaLinux:8 | All versions | 2022a-1.el8 |

## How do I fix ALBA-2022:1032?

Upgrade to a fixed version.

## Is ALBA-2022:1032 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2022:1032 is a vulnerability in tzdata, published on 23 Mar 2022. 
Exploitation: There is no known exploitation of ALBA-2022:1032 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2022:1032

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