← Retour
USN-7289-1
Vulnérabilité dans linux-azure (USN-7289-1)
Résumé
vulnérabilité dans linux-azure (USN-7289-1). Risque d'opérations non autorisées ou de divulgation. Atténuation : mise à jour vers `5.15.0-1081.90` ou plus.
Résumé IA snake-internal / snake-material-v2
Une vulnérabilité référencée **USN-7289-1** a été découverte dans linux-azure.
Risque d'opérations non autorisées ou de divulgation. Score CVSS : ?/10.
Action : mettez à jour linux-azure vers **5.15.0-1081.90** ou supérieur.
En cas de doute, contactez votre service informatique ou cherchez « linux-azure USN-7289-1 » sur le site de l'éditeur.
USN-7289-1 (linux-azure) —
Correctif : `5.15.0-1081.90` — 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 linux-azure.
📍 Périmètre concerné
linux-azure — .
🔥 Gravité
Gravité : ?. Risque d'opérations non autorisées ou de divulgation
🔧 Comment corriger
Mettre à jour vers **5.15.0-1081.90**.
🛡️ 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 'linux-azure' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `linux-azure` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade linux-azure to 5.15.0-1081.90ステージング環境で 5.15.0-1081.90 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Paquets affectés
Ubuntu:22.04:LTS
linux-azure
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1081.90"}]}]
Ubuntu:22.04:LTS
linux-azure-fde
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1081.90.1"}]}]
Ubuntu:22.04:LTS
linux-gkeop
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1060.68"}]}]
Ubuntu:22.04:LTS
linux-nvidia
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1072.73"}]}]
Ubuntu:22.04:LTS
linux-oracle
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1075.81"}]}]
Références
- advisory https://ubuntu.com/security/notices/USN-7289-1
- report https://ubuntu.com/security/CVE-2024-50072
- report https://ubuntu.com/security/CVE-2024-50074
- report https://ubuntu.com/security/CVE-2024-50085
- report https://ubuntu.com/security/CVE-2024-50101
- report https://ubuntu.com/security/CVE-2024-50193
- report https://ubuntu.com/security/CVE-2024-50249
- report https://ubuntu.com/security/CVE-2024-53042
- report https://ubuntu.com/security/CVE-2024-53097
- report https://ubuntu.com/security/CVE-2023-52913
- report https://ubuntu.com/security/CVE-2024-26718
- report https://ubuntu.com/security/CVE-2024-35887
- report https://ubuntu.com/security/CVE-2024-39497
- report https://ubuntu.com/security/CVE-2024-40953
- report https://ubuntu.com/security/CVE-2024-40965
- report https://ubuntu.com/security/CVE-2024-41066
- report https://ubuntu.com/security/CVE-2024-41080
- report https://ubuntu.com/security/CVE-2024-42252
- report https://ubuntu.com/security/CVE-2024-42291
- report https://ubuntu.com/security/CVE-2024-50010
- report https://ubuntu.com/security/CVE-2024-50036
- report https://ubuntu.com/security/CVE-2024-50058
- report https://ubuntu.com/security/CVE-2024-50082
- report https://ubuntu.com/security/CVE-2024-50083
- report https://ubuntu.com/security/CVE-2024-50086
- report https://ubuntu.com/security/CVE-2024-50099
- report https://ubuntu.com/security/CVE-2024-50103
- report https://ubuntu.com/security/CVE-2024-50110
- report https://ubuntu.com/security/CVE-2024-50115
- report https://ubuntu.com/security/CVE-2024-50116
- report https://ubuntu.com/security/CVE-2024-50117
- report https://ubuntu.com/security/CVE-2024-50127
- report https://ubuntu.com/security/CVE-2024-50128
- report https://ubuntu.com/security/CVE-2024-50131
- report https://ubuntu.com/security/CVE-2024-50134
- report https://ubuntu.com/security/CVE-2024-50141
- report https://ubuntu.com/security/CVE-2024-50142
- report https://ubuntu.com/security/CVE-2024-50143
- report https://ubuntu.com/security/CVE-2024-50148
- report https://ubuntu.com/security/CVE-2024-50150
- report https://ubuntu.com/security/CVE-2024-50151
- report https://ubuntu.com/security/CVE-2024-50153
- report https://ubuntu.com/security/CVE-2024-50154
- report https://ubuntu.com/security/CVE-2024-50156
- report https://ubuntu.com/security/CVE-2024-50160
- report https://ubuntu.com/security/CVE-2024-50162
- report https://ubuntu.com/security/CVE-2024-50163
- report https://ubuntu.com/security/CVE-2024-50167
- report https://ubuntu.com/security/CVE-2024-50168
- report https://ubuntu.com/security/CVE-2024-50171
- report https://ubuntu.com/security/CVE-2024-50182
- report https://ubuntu.com/security/CVE-2024-50185
- report https://ubuntu.com/security/CVE-2024-50192
- report https://ubuntu.com/security/CVE-2024-50194
- report https://ubuntu.com/security/CVE-2024-50195
- report https://ubuntu.com/security/CVE-2024-50196
- report https://ubuntu.com/security/CVE-2024-50198
- report https://ubuntu.com/security/CVE-2024-50199
- report https://ubuntu.com/security/CVE-2024-50201
- report https://ubuntu.com/security/CVE-2024-50202
- report https://ubuntu.com/security/CVE-2024-50205
- report https://ubuntu.com/security/CVE-2024-50208
- report https://ubuntu.com/security/CVE-2024-50209
- report https://ubuntu.com/security/CVE-2024-50218
- report https://ubuntu.com/security/CVE-2024-50229
- report https://ubuntu.com/security/CVE-2024-50230
- report https://ubuntu.com/security/CVE-2024-50232
- report https://ubuntu.com/security/CVE-2024-50233
- report https://ubuntu.com/security/CVE-2024-50234
- report https://ubuntu.com/security/CVE-2024-50236
- report https://ubuntu.com/security/CVE-2024-50237
- report https://ubuntu.com/security/CVE-2024-50244
- report https://ubuntu.com/security/CVE-2024-50245
- report https://ubuntu.com/security/CVE-2024-50247
- report https://ubuntu.com/security/CVE-2024-50251
- report https://ubuntu.com/security/CVE-2024-50257
- report https://ubuntu.com/security/CVE-2024-50259
- report https://ubuntu.com/security/CVE-2024-50262
- report https://ubuntu.com/security/CVE-2024-50265
- report https://ubuntu.com/security/CVE-2024-50267
- report https://ubuntu.com/security/CVE-2024-50268
- report https://ubuntu.com/security/CVE-2024-50269
- report https://ubuntu.com/security/CVE-2024-50273
- report https://ubuntu.com/security/CVE-2024-50278
- report https://ubuntu.com/security/CVE-2024-50279
- report https://ubuntu.com/security/CVE-2024-50282
- report https://ubuntu.com/security/CVE-2024-50287
- report https://ubuntu.com/security/CVE-2024-50290
- report https://ubuntu.com/security/CVE-2024-50292
- report https://ubuntu.com/security/CVE-2024-50295
- report https://ubuntu.com/security/CVE-2024-50296
- report https://ubuntu.com/security/CVE-2024-50299
- report https://ubuntu.com/security/CVE-2024-50301
- report https://ubuntu.com/security/CVE-2024-50302
- report https://ubuntu.com/security/CVE-2024-53052
- report https://ubuntu.com/security/CVE-2024-53055
- report https://ubuntu.com/security/CVE-2024-53058
- report https://ubuntu.com/security/CVE-2024-53059
- report https://ubuntu.com/security/CVE-2024-53061
- report https://ubuntu.com/security/CVE-2024-53063
- report https://ubuntu.com/security/CVE-2024-53066
- report https://ubuntu.com/security/CVE-2024-53088
- report https://ubuntu.com/security/CVE-2024-53101
- report https://ubuntu.com/security/CVE-2024-53104