GHSA-673q-mjm6-r5xr found in npm/[email protected]
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 1/5
- Tempo estimado
- Menos de uma hora
- Facilidade para iniciantes
- 78/100
- Tipo de issue
- Bug
- Clareza
- Claramente especificada
- Status de atividade
- Ativa
- Stack de tecnologia
- next.js
- Domínio
- security
Direção de pesquisa
O relatório identifica [email protected] como vulnerável e recomenda atualizar para a versão 16.4.1 ou posterior. Comece verificando no manifesto de pacotes e no arquivo de lock do repositório qual versão do Next.js está instalada. Em seguida, atualize a dependência e verifique a versão registrada. O trabalho estará concluído quando a dependência estiver na versão 16.4.1 ou superior e o relatório de vulnerabilidades não identificar mais essa versão.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
GHSA-673q-mjm6-r5xr found in npm/[email protected]
[!important]
Risk:3.40 (Low)
CVSS:9.5
Description
Impact
A vulnerability in applications using App router with Cache Component can lead to remote code execution. The application needs to have a use cache function that returns multiple typed arrays.
Workaround
There is no known workaround for affected applications with such use cache functions. You should upgrade immediately even if your application does not have similar functions.
Affected component
The vulnerability is in pkg:npm/[email protected], found in artifacts pkg:devguard/l3montree-cybersecurity/devguard/devguard-documentation, pkg:oci/devguard-documentation?repository_url=ghcr.io/l3montree-dev/devguard-documentation&arch=amd64&tag=main-amd64.
Recommended fix
Upgrade to version 16.4.1 or later.
# Update all vulnerable npm packages
npm audit fix
# Update only this package
npm install [email protected]
Additional guidance for mitigating vulnerabilities
Visit our guides on devguard.org
See more details...
Path to component
%%{init: { 'theme':'base', 'themeVariables': {
'primaryColor': '#F3F3F3',
'primaryTextColor': '#0D1117',
'primaryBorderColor': '#999999',
'lineColor': '#999999',
'secondaryColor': '#ffffff',
'tertiaryColor': '#ffffff'
} }}%%
flowchart TD
Your_application(["Your application"]) --- pkg_npm_next_16_3_8(["pkg:npm/next\@16.3.8"])
classDef default stroke-width:2px
| Risk Factor | Value | Description |
|---|---|---|
| Vulnerability Depth | 1 |
The vulnerability is in a direct dependency of your project. |
| EPSS | 0.00 % |
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days. |
| EXPLOIT | Not available |
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database. There are no script kiddies exploiting this vulnerability. |
| CVSS-BE | 9.0 |
|
| CVSS-B | 9.5 |
- The vulnerability can be exploited over the network without needing physical access. - It is easy for an attacker to exploit this vulnerability. - An attacker does not need any special privileges or access rights. - No user interaction is needed for the attacker to exploit this vulnerability. |
More details can be found in DevGuard
Interact with this vulnerability
You can use the following slash commands to interact with this vulnerability:
👍 Reply with this to acknowledge and accept the identified risk.
/accept I accept the risk of this vulnerability, because ...
⚠️ Mark the risk as false positive: Use one of these commands if you believe the reported vulnerability is not actually a valid issue.
/component-not-present The vulnerable component is not included in the artifact.
/vulnerable-code-not-present The component is present, but the vulnerable code is not included or compiled.
/vulnerable-code-not-in-execute-path The vulnerable code exists, but is never executed at runtime.
/vulnerable-code-cannot-be-controlled-by-adversary Built-in protections prevent exploitation of this vulnerability.
/inline-mitigations-already-exist The vulnerable code cannot be controlled or influenced by an attacker.
🔁 Reopen the risk: Use this command to reopen a previously closed or accepted vulnerability.
/reopen ...
- Linguagem predominante
- MDX
- Estrelas
- 8
- Forks
- 4
- Merge médio
- 3d 12min
- PRs com merge (30d)
- 6
Preparar o ambiente
- Inclui um Dockerfile ou arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
esphome/home-assistant-addon#274 ·
-
backend Low Priority subtask
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
Bearkat-Professionals/Software-Engineering-Project#87 ·
Mantenedores costumam responder em até 1 dia
-
Cloud environment origin check accepts an explicit default HTTPS port (:443) (follow-up to #30418)Abertaarea: cloud
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
manaflow-ai/cmux#31340 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
docker infra P1 security size:S
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
josephfung/curia#2408 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
drizzle-team/drizzle-orm#6620 · 1 comentário ·
Mantenedores costumam responder em até 2 dias