Vulnerability in gnutls28 (UBUNTU-CVE-2024-0553)
Summary
Vulnerability in gnutls28 (UBUNTU-CVE-2024-0553). Confidential information can be exposed externally. Mitigation: upgrade to 3.5.18-1ubuntu1.6+esm3 or later.
Original description
The description as published by the source.
A vulnerability was found in GnuTLS. The response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from the response times of ciphertexts with correct PKCS#1 v1.5 padding. This issue may allow a remote attacker to perform a timing side-channel attack in the RSA-PSK key exchange, potentially leading to the leakage of sensitive data. CVE-2024-0553 is designated as an incomplete resolution for CVE-2023-5981.
Source: OSV.dev (Open Source Vulnerabilities) OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as UBUNTU-CVE-2024-0553 has been found in gnutls28.
Confidential information can be exposed externally.
What to do: upgrade gnutls28 to 3.5.18-1ubuntu1.6+esm3 or later.
If unsure, ask your IT team or search "gnutls28 UBUNTU-CVE-2024-0553" on the vendor's site.
UBUNTU-CVE-2024-0553 (gnutls28)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.5.18-1ubuntu1.6+esm3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in gnutls28.
Check the vendor advisory for the affected versions of gnutls28.
Severity: ?. Confidential information can be exposed externally.
Update to 3.5.18-1ubuntu1.6+esm3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'gnutls28' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'gnutls28' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
gnutls28を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade gnutls28 to 3.5.18-1ubuntu1.6+esm3ステージング環境で 3.5.18-1ubuntu1.6+esm3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory ubuntu.com
- advisory ubuntu.com
- report ubuntu.com
- report gnutls.org
- report lists.gnupg.org
- report access.redhat.com
- report cve.org