← Retour
USN-7991-1
Vulnérabilité dans thunderbird (USN-7991-1)
Résumé
vulnérabilité dans thunderbird (USN-7991-1). Risque d'opérations non autorisées ou de divulgation. Atténuation : mise à jour vers `1:140.7.1+build1-0ubuntu0.22.04.1` ou plus.
Résumé IA snake-internal / snake-material-v2
Une vulnérabilité référencée **USN-7991-1** a été découverte dans thunderbird.
Risque d'opérations non autorisées ou de divulgation. Score CVSS : ?/10.
Action : mettez à jour thunderbird vers **1:140.7.1+build1-0ubuntu0.22.04.1** ou supérieur.
En cas de doute, contactez votre service informatique ou cherchez « thunderbird USN-7991-1 » sur le site de l'éditeur.
USN-7991-1 (thunderbird) —
Correctif : `1:140.7.1+build1-0ubuntu0.22.04.1` — appliquer immédiatement
Plan : 1) Audit SBOM, 2) Mise à jour staging→prod, 3) Surveillance WAF/proxy sur les endpoints affectés, 4) Recherche d'IOC dans les logs.
Réfs : voir GHSA / avis éditeur / version corrigée liés sur cette page.
❓ Quel est le problème
Une **vulnérabilité** (non classée) affecte thunderbird.
📍 Périmètre concerné
thunderbird — .
🔥 Gravité
Gravité : ?. Risque d'opérations non autorisées ou de divulgation
🔧 Comment corriger
Mettre à jour vers **1:140.7.1+build1-0ubuntu0.22.04.1**.
🛡️ Contournement
En attendant le correctif : désactivez la fonctionnalité concernée, appliquez des règles WAF, ou restreignez l'accès par ACL réseau.
🔍 Détection
Recherchez dans les logs des requêtes correspondant aux IOC connus de cette CVE. Auditez les SBOM/dépendances.
Actions de réponse (7 étapes)
Étapes concrètes et exemples de commandes que les équipes SOC/SRE doivent exécuter dans l'ordre
-
1Identify exposure identify
grep -r 'thunderbird' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `thunderbird` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade thunderbird to 1:140.7.1+build1-0ubuntu0.22.04.1ステージング環境で 1:140.7.1+build1-0ubuntu0.22.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Paquets affectés
Ubuntu:22.04:LTS
thunderbird
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:140.7.1+build1-0ubuntu0.22.04.1"}]}]
Références
- advisory https://ubuntu.com/security/notices/USN-7991-1
- report https://ubuntu.com/security/CVE-2024-9396
- report https://ubuntu.com/security/CVE-2024-9397
- report https://ubuntu.com/security/CVE-2024-9398
- report https://ubuntu.com/security/CVE-2024-9399
- report https://ubuntu.com/security/CVE-2024-9400
- report https://ubuntu.com/security/CVE-2024-9402
- report https://ubuntu.com/security/CVE-2024-9403
- report https://ubuntu.com/security/CVE-2024-10460
- report https://ubuntu.com/security/CVE-2024-10461
- report https://ubuntu.com/security/CVE-2024-10462
- report https://ubuntu.com/security/CVE-2024-10464
- report https://ubuntu.com/security/CVE-2024-10465
- report https://ubuntu.com/security/CVE-2024-10466
- report https://ubuntu.com/security/CVE-2024-10467
- report https://ubuntu.com/security/CVE-2024-10468
- report https://ubuntu.com/security/CVE-2024-50336
- report https://ubuntu.com/security/CVE-2025-0237
- report https://ubuntu.com/security/CVE-2025-0239
- report https://ubuntu.com/security/CVE-2025-0240
- report https://ubuntu.com/security/CVE-2025-0241
- report https://ubuntu.com/security/CVE-2025-0243
- report https://ubuntu.com/security/CVE-2025-0247
- report https://ubuntu.com/security/CVE-2025-1018
- report https://ubuntu.com/security/CVE-2025-1019
- report https://ubuntu.com/security/CVE-2025-1020
- report https://ubuntu.com/security/CVE-2025-1942
- report https://ubuntu.com/security/CVE-2025-1943
- report https://ubuntu.com/security/CVE-2025-3031
- report https://ubuntu.com/security/CVE-2025-3032
- report https://ubuntu.com/security/CVE-2025-3034
- report https://ubuntu.com/security/CVE-2025-4085
- report https://ubuntu.com/security/CVE-2025-4088
- report https://ubuntu.com/security/CVE-2025-4089
- report https://ubuntu.com/security/CVE-2025-4092
- report https://ubuntu.com/security/CVE-2025-5270
- report https://ubuntu.com/security/CVE-2025-5271
- report https://ubuntu.com/security/CVE-2025-5272
- report https://ubuntu.com/security/CVE-2025-5283
- report https://ubuntu.com/security/CVE-2025-6427
- report https://ubuntu.com/security/CVE-2025-6432
- report https://ubuntu.com/security/CVE-2025-6433
- report https://ubuntu.com/security/CVE-2025-6434
- report https://ubuntu.com/security/CVE-2025-6435
- report https://ubuntu.com/security/CVE-2025-6436
- report https://ubuntu.com/security/CVE-2025-8027
- report https://ubuntu.com/security/CVE-2025-8028
- report https://ubuntu.com/security/CVE-2025-8029
- report https://ubuntu.com/security/CVE-2025-8030
- report https://ubuntu.com/security/CVE-2025-8031
- report https://ubuntu.com/security/CVE-2025-8032
- report https://ubuntu.com/security/CVE-2025-8033
- report https://ubuntu.com/security/CVE-2025-8034
- report https://ubuntu.com/security/CVE-2025-8035
- report https://ubuntu.com/security/CVE-2025-8036
- report https://ubuntu.com/security/CVE-2025-8037
- report https://ubuntu.com/security/CVE-2025-8038
- report https://ubuntu.com/security/CVE-2025-8039
- report https://ubuntu.com/security/CVE-2025-8040
- report https://ubuntu.com/security/CVE-2025-9179
- report https://ubuntu.com/security/CVE-2025-9180
- report https://ubuntu.com/security/CVE-2025-9181
- report https://ubuntu.com/security/CVE-2025-9182
- report https://ubuntu.com/security/CVE-2025-9184
- report https://ubuntu.com/security/CVE-2025-9185
- report https://ubuntu.com/security/CVE-2025-10527
- report https://ubuntu.com/security/CVE-2025-10528
- report https://ubuntu.com/security/CVE-2025-10529
- report https://ubuntu.com/security/CVE-2025-10532
- report https://ubuntu.com/security/CVE-2025-10533
- report https://ubuntu.com/security/CVE-2025-10536
- report https://ubuntu.com/security/CVE-2025-10537
- report https://ubuntu.com/security/CVE-2025-11708
- report https://ubuntu.com/security/CVE-2025-11709
- report https://ubuntu.com/security/CVE-2025-11710
- report https://ubuntu.com/security/CVE-2025-11711
- report https://ubuntu.com/security/CVE-2025-11712
- report https://ubuntu.com/security/CVE-2025-11713
- report https://ubuntu.com/security/CVE-2025-11714
- report https://ubuntu.com/security/CVE-2025-11715
- report https://ubuntu.com/security/CVE-2025-13012
- report https://ubuntu.com/security/CVE-2025-13013
- report https://ubuntu.com/security/CVE-2025-13014
- report https://ubuntu.com/security/CVE-2025-13015
- report https://ubuntu.com/security/CVE-2025-13016
- report https://ubuntu.com/security/CVE-2025-13017
- report https://ubuntu.com/security/CVE-2025-13018
- report https://ubuntu.com/security/CVE-2025-13019
- report https://ubuntu.com/security/CVE-2025-13020
- report https://ubuntu.com/security/CVE-2025-14321
- report https://ubuntu.com/security/CVE-2025-14322
- report https://ubuntu.com/security/CVE-2025-14323
- report https://ubuntu.com/security/CVE-2025-14324
- report https://ubuntu.com/security/CVE-2025-14325
- report https://ubuntu.com/security/CVE-2025-14327
- report https://ubuntu.com/security/CVE-2025-14328
- report https://ubuntu.com/security/CVE-2025-14329
- report https://ubuntu.com/security/CVE-2025-14330
- report https://ubuntu.com/security/CVE-2025-14331
- report https://ubuntu.com/security/CVE-2026-0818
- report https://ubuntu.com/security/CVE-2026-0877
- report https://ubuntu.com/security/CVE-2026-0878
- report https://ubuntu.com/security/CVE-2026-0879
- report https://ubuntu.com/security/CVE-2026-0880
- report https://ubuntu.com/security/CVE-2026-0882
- report https://ubuntu.com/security/CVE-2026-0883
- report https://ubuntu.com/security/CVE-2026-0884
- report https://ubuntu.com/security/CVE-2026-0885
- report https://ubuntu.com/security/CVE-2026-0886
- report https://ubuntu.com/security/CVE-2026-0887
- report https://ubuntu.com/security/CVE-2026-0890
- report https://ubuntu.com/security/CVE-2026-0891