We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reference implementation of Joyent's HTTP Signature scheme.
Library home page: https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/zaproxy/node_modules/http-signature/package.json
Dependency Hierarchy:
Found in HEAD commit: cf912e826f09ac42f1452743dde64dc7a5b425f5
Found in base branch: master
http-signature before version 1.0.0 are vulnerable to timing attack, which may lead to information disclosure.
Publish Date: 2015-01-22
URL: WS-2017-0266
Base Score Metrics:
Type: Upgrade version
Origin: TritonDataCenter/node-http-signature#36
Release Date: 2015-01-22
Fix Resolution: 1.0.0
The text was updated successfully, but these errors were encountered:
No branches or pull requests
WS-2017-0266 - Low Severity Vulnerability
Vulnerable Library - http-signature-0.10.1.tgz
Reference implementation of Joyent's HTTP Signature scheme.
Library home page: https://registry.npmjs.org/http-signature/-/http-signature-0.10.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/zaproxy/node_modules/http-signature/package.json
Dependency Hierarchy:
Found in HEAD commit: cf912e826f09ac42f1452743dde64dc7a5b425f5
Found in base branch: master
Vulnerability Details
http-signature before version 1.0.0 are vulnerable to timing attack, which may lead to information disclosure.
Publish Date: 2015-01-22
URL: WS-2017-0266
CVSS 3 Score Details (3.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: TritonDataCenter/node-http-signature#36
Release Date: 2015-01-22
Fix Resolution: 1.0.0
The text was updated successfully, but these errors were encountered: