Vulnerability in bouncycastle (USN-8108-1)

Summary

vulnerability in bouncycastle (USN-8108-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `1.51-4ubuntu1+esm1` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **USN-8108-1** has been found in bouncycastle. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade bouncycastle to **1.51-4ubuntu1+esm1** or later. If unsure, ask your IT team or search "bouncycastle USN-8108-1" on the vendor's site.

USN-8108-1 (bouncycastle) — Patched: `1.51-4ubuntu1+esm1` — 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 bouncycastle.

📍 Affected scope

bouncycastle — .

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **1.51-4ubuntu1+esm1**.

🛡️ 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 'bouncycastle' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

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

Affected packages

Ubuntu:Pro:16.04:LTS bouncycastle

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.51-4ubuntu1+esm1"}]}]

Ubuntu:Pro:18.04:LTS bouncycastle

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.59-1ubuntu0.1~esm1"}]}]

Ubuntu:Pro:20.04:LTS bouncycastle

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.61-1ubuntu0.1~esm1"}]}]

Ubuntu:Pro:22.04:LTS bouncycastle

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.68-5ubuntu0.1~esm1"}]}]

Ubuntu:Pro:24.04:LTS bouncycastle

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.77-1ubuntu0.1~esm1"}]}]

References

advisory https://ubuntu.com/security/notices/USN-8108-1
report https://ubuntu.com/security/CVE-2023-33201
report https://ubuntu.com/security/CVE-2024-29857
report https://ubuntu.com/security/CVE-2024-30171
report https://ubuntu.com/security/CVE-2024-30172
report https://ubuntu.com/security/CVE-2024-34447
report https://ubuntu.com/security/CVE-2025-8916