Skip to content
Fencer Vulns
high 7.5

CVE-2017-16005 json

Header Forgery in http-signature

published 2018-06-04 8 y ago modified 2026-06-17 4 mo ago also GHSA-q257-vv4p-fg92 , EUVD-2018-0766

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm http-signature 0.10.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-16005 updated cvss 7.5

nodejs-http-signature: HTTP header forgery

  • Red Hat Enterprise Linux 8 nodejs-http-signature
    affected: no fix planned “Will not fix”
  • Red Hat Mobile Application Platform 4 nodejs-http-signature Red Hat OpenShift Enterprise 3 nodejs-http-signature Red Hat Software Collections rh-nodejs4-nodejs-http-signature, rh-nodejs6-nodejs-http-signature
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm http-signature
<0.10.0
0.10.0

Affected products

  • HackerOne http-signature node module

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.