GitHub Tightens npm Publishing After Flaw Left 1,500+ Packages Vulnerable to Hijacking
GitHub has taken the step of expiring unvalidated npm trusted publishing configurations 48 hours after creation after researchers found that it was possible for an attacker to push new versions of a different user's package without having to steal their credentials. "Your configuration becomes validated and exempt from expiry after its first successful publish," the Microsoft-owned subsidiary
Se muestra el contenido original; la traduccion localizada aun no esta disponible.
Qué ocurrió
GitHub has taken the step of expiring unvalidated npm trusted publishing configurations 48 hours after creation after researchers found that it was possible for an attacker to push new versions of a different user's package without having to steal their credentials. "Your configuration becomes validated and exempt from expiry after its first successful publish," the Microsoft-owned subsidiary
Por que importa
The development may change operating conditions or market expectations around Microsoft. Further confirmation and measurable outcomes matter.
Entidades afectadas
Ver evidencia
1 articulos · 1 informe original · 1 independientes
- The Hacker NewsFuente primaria · Respalda · EN · 100%GitHub Tightens npm Publishing After Flaw Left 1,500+ Packages Vulnerable to Hijacking ↗
Afirmaciones
- GitHub Tightens npm Publishing After Flaw Left 1,500+ Packages Vulnerable to Hijacking Observado
Conflictos
No se detectaron conflictos importantes en la evidencia disponible.
Cronología
- Primera publicación
Movimiento del mercado posterior al evento
La reacción del mercado aún no está disponible para este activo y periodo.