Vulnerability in gnutls26 (UBUNTU-CVE-2018-10844)

Summary

Vulnerability in gnutls26 (UBUNTU-CVE-2018-10844). Confidential information can be exposed externally. Mitigation: upgrade to 3.4.10-4ubuntu1.5 or later.

Original description

The description as published by the source.

It was found that the GnuTLS implementation of HMAC-SHA-256 was vulnerable to a Lucky thirteen style attack. Remote attackers could use this flaw to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data using crafted packets.

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-2018-10844 has been found in gnutls26.
Confidential information can be exposed externally.
What to do: upgrade gnutls26 to 3.4.10-4ubuntu1.5 or later.
If unsure, ask your IT team or search "gnutls26 UBUNTU-CVE-2018-10844" on the vendor's site.

UBUNTU-CVE-2018-10844 (gnutls26)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.4.10-4ubuntu1.5 — 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 gnutls26.

📍 Affected scope

Check the vendor advisory for the affected versions of gnutls26.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 3.4.10-4ubuntu1.5.

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

Affected packages

Ubuntu:Pro:14.04:LTS gnutls26

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

Ubuntu:16.04:LTS gnutls28

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

Ubuntu:18.04:LTS gnutls28

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.18-1ubuntu1.1"}]}]

References

advisory ubuntu.com
report ubuntu.com
report eprint.iacr.org
report cve.org