critical

SUSE-SU-2022:0091-1

Security update for apache2

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

No source gives a CVSS score.

Trivy's own label is CRITICAL. Rated critical by SUSE.

Description

This update for apache2 fixes the following issues: Apache2 was updated to the current stable version 2.4.51 (jsc#SLE-22733 jsc#SLE-22849) It fixes all CVEs and selected bugs represented by patches found between 2.4.23 and 2.4.51. See https://downloads.apache.org/httpd/CHANGES_2.4 for a complete change log. Also fixed: - CVE-2021-44224: Fixed NULL dereference or SSRF in forward proxy configurations (bsc#1193943) - CVE-2021-44790: Fixed buffer overflow when parsing multipart content in mod_lua (bsc#1193942)

Affected packages and fixed versions

Source	Package	Fixed in
SUSE Linux Enterprise 15.2	apache2, apache2-devel, apache2-doc and 3 more	2.4.51-3.37.1
SUSE Linux Enterprise 15.3	apache2, apache2-devel, apache2-doc and 4 more	2.4.51-3.37.1

Show all 13 entries from 2 sources

Source	Package	Fixed in
SUSE Linux Enterprise 15.2	apache2	2.4.51-3.37.1
SUSE Linux Enterprise 15.2	apache2-devel	2.4.51-3.37.1
SUSE Linux Enterprise 15.2	apache2-doc	2.4.51-3.37.1
SUSE Linux Enterprise 15.2	apache2-prefork	2.4.51-3.37.1
SUSE Linux Enterprise 15.2	apache2-utils	2.4.51-3.37.1
SUSE Linux Enterprise 15.2	apache2-worker	2.4.51-3.37.1
SUSE Linux Enterprise 15.3	apache2	2.4.51-3.37.1
SUSE Linux Enterprise 15.3	apache2-devel	2.4.51-3.37.1
SUSE Linux Enterprise 15.3	apache2-doc	2.4.51-3.37.1
SUSE Linux Enterprise 15.3	apache2-event	2.4.51-3.37.1
SUSE Linux Enterprise 15.3	apache2-prefork	2.4.51-3.37.1
SUSE Linux Enterprise 15.3	apache2-utils	2.4.51-3.37.1
SUSE Linux Enterprise 15.3	apache2-worker	2.4.51-3.37.1

References

What Attestkeep does with this

Inside your cluster, without you opening a spreadsheet.

KnowsThe scanner refreshes its vulnerability database every six hours.

FindsEvery admitted image is rescanned every 24 hours by default (scan.rescanInterval). When Trivy rates this vulnerability critical for the image's package source, it appears in the image's findings by name. Findings without a fix are left out unless includeUnfixed is on.

Tells youA critical_finding event goes to the channels subscribed to it: e-mail, Slack, Teams, a webhook, Jira, GitLab or GitHub.

RefusesWith a policy that blocks critical findings, a pod with this image is refused at admission, a rollback to it included. Pods already running are not evicted.

RecordsEach decision is recorded with the policy that ran and its hash, then sealed under a signed checkpoint.

Try Attestkeep

Read the docs