security-policy: the Kubernetes SECURITY_CONTACTS convention and a SECURITY.md with an obfuscated address + PGP fingerprint are not recognised

Aperta
  • Qualcosa non va?
#242 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
devtools, security

Direzione di ricerca

The payload does not name the source file that implements the security-policy check, so first locate it in the Python validator. Reproduce the two cases: a directory containing only a SECURITY_CONTACTS file with the two Kubernetes header lines, and a SECURITY.md with a ## Reporting a Vulnerability heading and an obfuscated address. Done when both produce the expected result and the expectations in corpus/ are updated to match. The issue leaves open whether the heading alone should count, so confirm that with maintainers first.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

kubespray follows the Kubernetes organisation's SECURITY_CONTACTS file (header points to kubernetes.io/security, private reporting to the Product Security Committee) → WARN "no security policy"; Catch2's SECURITY.md has a "Reporting a Vulnerability" section with a spam-obfuscated email and a PGP fingerprint → WARN "does not say how to report".

Evidence from the corpus audit

kubernetes-sigs/kubespray / security-policy
  • kind: UNSUPPORTED
  • actual: WARN "no security policy / add a SECURITY.md that says how to report a vulnerability privately"
  • expected: PASS or at least a mention: the repository follows the Kubernetes-organisation convention,
    SECURITY_CONTACTS, whose header tells reporters to follow https://kubernetes.io/security/ (private reporting to
    the Kubernetes Product Security Committee). Every kubernetes/ and kubernetes-sigs/ repository has this file
    (kubernetes/examples in this batch has both and passes on its SECURITY.md).
  • evidence: SECURITY_CONTACTS:10-11: # DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE /
    # INSTRUCTIONS AT https://kubernetes.io/security/; find . -iname 'SECURITY*' → only ./SECURITY_CONTACTS.
  • repro: a repo with SECURITY_CONTACTS containing those two header lines and no SECURITY.md.
  • confidence: medium
catchorg/Catch2 / security-policy
  • kind: FALSE_NEGATIVE
  • actual: WARN: SECURITY.md does not say how to report a vulnerability
  • expected: PASS: SECURITY.md has a "Reporting a Vulnerability" section with a (spam-obfuscated) email address and
    a PGP fingerprint.
  • evidence: SECURITY.md:12: ## Reporting a Vulnerability; :18-20: However, if you find one you send email to martin <dot> horenovsky <at> / gmail <dot> com. If you want to encrypt the email, my pgp key is /
    `E29C 46F3 B8A7 5028 6079 3B7D ECC9 C20E 314B 2360`.
  • repro: a SECURITY.md with "## Reporting a Vulnerability" and name <at> example <dot> com; expect PASS (or
    accept the heading alone as "says how").
  • confidence: medium

Found by the regression-corpus audit (235 real repositories, one or more per ecosystem profile; corpus and expected results in corpus/). Evidence is quoted from the audited checkouts at the commits pinned in corpus/projects.toml; <checkouts>/<owner>__<repo> is such a checkout.

🤖 Generated with Claude Code

https://claude.ai/code/session_01ByTXNqDWdM7HzezrFtEvQt

Lingua principale
Python
Stelle
4
Fork
1
Merge medio
10h 41m
PR unite (30g)
79

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cpp-best-practices/project_validator

Tutte le issue di cpp-best-practices/project_validator

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.