Files
management/docs/issues/0051-cve-remediation-pass.md
T
Thore CimbalandClaude Opus 5 667f69d93f chore(issues): record the mirror addresses from the first full run
The mirror created the seven issues that had never reached the board
(management#33-39) and wrote each new iid back into its file. Without the
writeback the next run would create duplicates instead of recognising its own
work.

Group check after the run: the issue drift class is empty - 27 findings down to
20, 7 hints to 0, and not a single GitLab issue without a canonical file. What
remains is unrelated to the board: seventeen commit-hygiene findings parked in
#0053 and three component declarations.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-18 12:00:00 +00:00

35 lines
1.4 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
type: issue
id: "0051"
status: open
created: 2026-08-14
milestone: M5
priority: high
area: security
related: [docs/issues/0025-deploy-uebergabe-cve-alarme-aggregiert-receiver.md, docs/aar/2026-08-01-cve-pipeline-gitops47.md]
gitlab_iid: "37"
---
# CVE-Remediation-Pass: Schwachstellen-Report abarbeiten
## Problem / Motivation
Die Trivy-CVE-Pipeline meldet über 29 Images ~5400 CVEs (**126 CRITICAL, 1222 HIGH**, Rest
MEDIUM/LOW), Spitzenreiter `goauthentik/server:2026.2.3` mit **369 CRIT+HIGH**. #0025 deckt
nur die Alarm-Zustellung ab — die eigentliche **Behebung** fehlte als eigenes Issue.
## Acceptance
- Nach **Schwere × Fixbarkeit** priorisiert (CRITICAL zuerst; „fixed available" vor
won't-fix; exponiert vor intern) — Methode als Runbook `/betrieb/sicherheit` im Wiki.
- Top-Offender mit verfügbarem Fix behoben: v.a. **Authentik-Update** (mit Backup), eigene
Images (`axion-backup`, `axion-secret-rotation`, `clamav-http-scanner`) auf aktueller Base
neu gebaut, ESS-Bump → Delta im Grafana-CVE-Dashboard sichtbar.
- won't-fix / nicht-exponierte CVEs mitigiert oder in **`.trivyignore` mit Begründung +
Review-Datum** suppress-t.
- Re-Scan zeigt deutlich gesunkene CRITICAL/HIGH.
## Notes
Hängt eng an der Update-Kadenz (#0052) — Updaten ist der Haupthebel gegen die CVEs.
Methode/Runbook: `/betrieb/sicherheit`; Update-Prozess: `/betrieb/upgrades`.