Repository advisory GHSA-7v25-vcp6-4hcr not in global Advisory Database
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 30/100
Línea de trabajo
This is a request for the GitHub Advisory Database curation team to review a published repository advisory for inclusion. The issue is about process and database synchronization, not code changes. A newcomer would need to understand the advisory database ingestion pipeline, the criteria for inclusion, and how to escalate a stuck advisory. Check the repository's contribution guidelines and existing similar issues to see how curation requests are handled. 'Done' means the advisory appears in the global database.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
I maintain tumf/mcp-shell-server. Repository advisory GHSA-7v25-vcp6-4hcr was published on 2026-09-19 and remains absent from the global GitHub Advisory Database more than 72 hours later.
Advisory
- Repository advisory: https://github.com/tumf/mcp-shell-server/security/advisories/GHSA-7v25-vcp6-4hcr
- Package:
mcp-shell-server(pip) - Affected versions:
<= 1.1.11 - Patched version:
1.1.12 - CWE: CWE-88
- Severity: High
- Reporter credit: accepted
The advisory describes Git global options with separated values causing the validator to misidentify the subcommand, allowing persistent git config writes and later command execution when git is allowlisted. Version 1.1.12 fixes the affected parser state.
Current state
- Repository advisory state:
published cve_id:nullsubmission.accepted:falseGET /advisories/GHSA-7v25-vcp6-4hcr:404 Not Found- Advisory
updated_at:2026-09-19T01:21:39Z
Request
Could the curation team review this published repository advisory for inclusion in the global GitHub Advisory Database?
I have not requested a CVE because database inclusion and CVE assignment are separate. If a CVE or additional information is required for curation, please advise.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 2.5k
- Forks
- 772
- Merge medio
- 3 d 15 h
- PR fusionados (30 d)
- 46
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/advisory-database
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
github/advisory-database#9255 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
github/advisory-database#9164 · 1 reacción ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
github/advisory-database#8994 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
github/advisory-database#8898 · 4 comentarios · 1 reacción ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
github/advisory-database#8841 ·
Todos los issues de github/advisory-database
Issues similares
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Nmap
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
-
Mend: dependency security vulnerability untriaged
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
blocklist removal
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
MetaMask/eth-phishing-detect#296544 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Azure/azure-functions-docker#1257 ·