Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

🔒 [IBM OSPO Security Notification] — IBM/secrets-manager-java-sdk

Aberta
#210 2 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
55/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
java, javascript
Domínio
security

Direção de pesquisa

Review the Dependabot alerts and locate the dependency manifest or lockfile containing ip-address and undici. Update each affected package to the listed patched version, then run the repository's available dependency checks and confirm that all six alerts are resolved.

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

Descrição

security

🔒 [IBM OSPO Security Notification] — IBM/secrets-manager-java-sdk

Action required: Remediate the alerts listed below before their SLA deadline.
This issue will be closed automatically once all alerts are resolved.

SLA policy: critical = 7 days, high = 30 days, medium = 90 days, low = no deadline.
Alerts at or above medium severity will trigger a warning comment before the deadline and
repo archiving if unresolved. Low-severity alerts are tracked here for visibility only —
they will never trigger warnings or archiving.

💡 Tip: To have Dependabot automatically open fix PRs for dependency alerts, enable
Dependabot security updates in your repo settings:
Settings → Advanced Security → Dependabot security updates → Enable.

📖 New to this issue? See the Security Issue Guide for a full explanation of what this issue means and what you need to do.

Attention: @IdanAdar @secrets-automation-dev

Dependabot Alerts
Severity CVE/GHSA Package Affected Patched Deadline Fix PR
🟠 high CVE-2026-69192 ip-address <= 10.3.0 10.3.1 2026-10-30 —
🟡 medium CVE-2026-54272 ip-address >= 10.1.1, <= 10.2.0 10.2.1 2026-12-29 —
🟡 medium CVE-2026-69198 ip-address >= 10.1.1, <= 10.2.1 10.2.2 2026-12-29 —
🟡 medium CVE-2026-16728 undici < 6.28.0 6.28.0 2026-12-29 —
🟡 medium CVE-2026-15157 undici < 6.28.0 6.28.0 2026-12-29 —
🟡 medium CVE-2026-16729 undici < 6.28.0 6.28.0 2026-12-29 —
🟡 medium CVE-2026-101910 ip-address >= 10.2.0, <= 10.5.0 10.5.1 2026-12-28 —
🟡 medium CVE-2026-101913 ip-address <= 10.5.0 10.5.1 2026-12-29 —
🟡 medium CVE-2026-102277 brace-expansion >= 4.0.0, < 5.0.12 5.0.12 2026-12-29 —
🟡 medium CVE-2026-101912 ip-address <= 10.7.0 10.7.1 2026-12-29 —
🔵 low CVE-2026-18540 undici < 6.28.1 6.28.1 — —
Code Scanning Alerts

No open code scanning alerts.

Secret Scanning Alerts

No open secret scanning alerts.


Linguagem predominante
Java
Estrelas
2
Forks
8
Merge médio
5d 11h
PRs com merge (30d)
11

Preparar o ambiente

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 IBM/secrets-manager-java-sdk

Todas as issues de IBM/secrets-manager-java-sdk

Issues semelhantes

Mais issues de Java

Receba novas issues na sua caixa de entrada

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