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

Aberta
  • Algo errado?
#242 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
45/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
python
Domínio
devtools, security

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
Python
Estrelas
4
Forks
1
Merge médio
10h 41min
PRs com merge (30d)
79

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de cpp-best-practices/project_validator

Todas as issues de cpp-best-practices/project_validator

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.