# ALBA-2021:4003: tzdata bug fix and enhancement update

> Update tzdata to version 2021e to correct time zone rules for Fiji and Palestine, ensuring accurate time calculations.

- **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:** 26 Oct 2021

## What is ALBA-2021:4003?

ALBA-2021:4003 is a vulnerability in tzdata-java, published on 26 Oct 2021. 

### Official description

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

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

* The Pacific/Fiji timezone has suspended daylight saving time (DST) for the 2021/2022 season.

* The 'zic -r' command now marks unspecified timestamps with "-00".

* Palestine will end daylight saving time (DST) on October 29, 2021 at 01:00, rather than the predicted October 30, 2021.

(BZ#2015242, BZ#2015246, BZ#2016369)

## Which versions are affected by ALBA-2021:4003?


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

## How do I fix ALBA-2021:4003?

Upgrade to a fixed version.

## Is ALBA-2021:4003 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2021:4003 is a vulnerability in tzdata-java, published on 26 Oct 2021. 
Exploitation: There is no known exploitation of ALBA-2021:4003 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2021:4003

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