Vulnerability in gnutls28 (UBUNTU-CVE-2023-0361)

Summary

Vulnerability in gnutls28 (UBUNTU-CVE-2023-0361). Confidential information can be exposed externally. Mitigation: upgrade to 3.6.13-2ubuntu1.8 or later.

Original description

The description as published by the source.

A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection.

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-2023-0361 has been found in gnutls28.
Confidential information can be exposed externally.
What to do: upgrade gnutls28 to 3.6.13-2ubuntu1.8 or later.
If unsure, ask your IT team or search "gnutls28 UBUNTU-CVE-2023-0361" on the vendor's site.

UBUNTU-CVE-2023-0361 (gnutls28)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.6.13-2ubuntu1.8 — 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.

❓ What is the problem

A vulnerability (unclassified) exists in gnutls28.

📍 Affected scope

Check the vendor advisory for the affected versions of gnutls28.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 3.6.13-2ubuntu1.8.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

1
Identify exposure identify
```
grep -r 'gnutls28' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で gnutls28 を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade gnutls28 to 3.6.13-2ubuntu1.8
```
ステージング環境で 3.6.13-2ubuntu1.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:16.04:LTS gnutls28

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:Pro:18.04:LTS gnutls28

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:20.04:LTS gnutls28

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.6.13-2ubuntu1.8"}]}]

Ubuntu:22.04:LTS gnutls28

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.7.3-4ubuntu1.2"}]}]

References

advisory ubuntu.com
report ubuntu.com
report gnutls.org
report cve.org