Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Buffer no longer performs length check for hex strings in node v8.x #52

Closed
melloc opened this issue Jul 31, 2018 · 1 comment
Closed

Buffer no longer performs length check for hex strings in node v8.x #52

melloc opened this issue Jul 31, 2018 · 1 comment
Assignees
@melloc

Comments

@melloc
Copy link
Contributor

melloc commented Jul 31, 2018

As of nodejs/node#12012, Buffer will no longer throw when given a hex string of an invalid length. sshpk was relying on this check for rejecting bad MD5 fingerprints, so we'll need to perform the check ourselves now.
@melloc melloc self-assigned this Jul 31, 2018
@melloc melloc changed the title Buffer no longer performs length check in node v8 Buffer no longer performs length check for hex strings in node v8 Jul 31, 2018
@melloc melloc changed the title Buffer no longer performs length check for hex strings in node v8 Buffer no longer performs length check for hex strings in node v8.x Jul 31, 2018
@melloc
Copy link
Contributor Author

melloc commented Jul 31, 2018

CR at https://cr.joyent.us/4608

joyent-automation pushed a commit that referenced this issue Oct 10, 2018
@melloc
#52 Buffer no longer performs length check for hex strings in node v8.x
1088992 
Reviewed by: Alex Wilson <[email protected]>
Approved by: Alex Wilson <[email protected]>
This was referenced Oct 12, 2018
Closed
Closed
Closed
Closed
Merged
Closed
Merged
Closed
Merged
Merged
Merged
Closed
Merged
Merged
Closed
Merged
Merged
Merged
Closed
Merged
Turbo87 pushed a commit to Turbo87/igc-parser that referenced this issue Oct 15, 2018
@dependabot @Turbo87
[Security] Bump sshpk from 1.13.1 to 1.15.1 (#63)
a0a31ad 
Bumps [sshpk](https://github.com/joyent/node-sshpk) from 1.13.1 to 1.15.1. **This update includes security fixes.**
<details>
<summary>Vulnerabilities fixed</summary>

*Sourced from [The Sonatype OSS Index](https://ossindex.sonatype.org/vuln/fc393f9f-282f-4bc9-953b-d7e4b48352e9).*

> **CWE-400: Uncontrolled Resource Consumption ('Resource Exhaustion')**
> The software does not properly restrict the size or amount of resources that are requested or influenced by an actor, which can be used to consume more resources than intended.
> 
> Affected versions: <1.14.1

*Sourced from The GitHub Vulnerability Alert Database.*

> **CVE-2018-3737**
> See https://nvd.nist.gov/vuln/detail/CVE-2018-3737.
> 
> Affected versions: < 1.13.2

*Sourced from [The Node Security Working Group](https://github.com/nodejs/security-wg/blob/master/vuln/npm/401.json).*

> **Denial of Service**
> `sshpk` is vulnerable to ReDoS when parsing crafted invalid public keys
> 
> Affected versions: <=1.13.1

</details>
<details>
<summary>Release notes</summary>

*Sourced from [sshpk's releases](https://github.com/joyent/node-sshpk/releases).*

> ## v1.14.1
>  * Remove all remaining usage of jodid25519 (abandoned dep)
>  * Add support for DNSSEC key format
>  * Add support for Ed25519 keys in PEM format (according to draft-curdle-pkix)
>  * Fixes for X.509 encoding issues (asn.1 NULLs in RSA certs, cert string type mangling)
>  * Performance issues parsing long SSH public keys
</details>
<details>
<summary>Commits</summary>

- [`2ab4f2a`](TritonDataCenter/node-sshpk@2ab4f2a) TritonDataCenter/node-sshpk#56 md5 fingerprints not quite right
- [`026ef47`](TritonDataCenter/node-sshpk@026ef47) TritonDataCenter/node-sshpk#53 stop using optional deps to fix webpack
- [`53e23fe`](TritonDataCenter/node-sshpk@53e23fe) TritonDataCenter/node-sshpk#50 Support PKCS#5 AES-256-CBC encrypted private keys
- [`6b68d49`](TritonDataCenter/node-sshpk@6b68d49) TritonDataCenter/node-sshpk#54 want API for accessing x509 extensions
- [`1088992`](TritonDataCenter/node-sshpk@1088992) TritonDataCenter/node-sshpk#52 Buffer no longer performs length check for hex strings i...
- [`6ec6f9d`](TritonDataCenter/node-sshpk@6ec6f9d) TritonDataCenter/node-sshpk#38 want support for more obscure DN OIDs
- [`1cc4c99`](TritonDataCenter/node-sshpk@1cc4c99) TritonDataCenter/node-sshpk#51 package.json repository does not point to Joyent
- [`175758a`](TritonDataCenter/node-sshpk@175758a) TritonDataCenter/node-sshpk#46 Use Buffer.(from|alloc) instead of deprecated Buffer API
- [`6edb37c`](TritonDataCenter/node-sshpk@6edb37c) Release 1.14.0
- [`46065d3`](TritonDataCenter/node-sshpk@46065d3) TritonDataCenter/node-sshpk#44 Performance issues parsing long SSH public keys
- Additional commits viewable in [compare view](TritonDataCenter/node-sshpk@v1.13.1...v1.15.1)
</details>
<br />

[![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=sshpk&package-manager=npm_and_yarn&previous-version=1.13.1&new-version=1.15.1)](https://dependabot.com/compatibility-score.html?dependency-name=sshpk&package-manager=npm_and_yarn&previous-version=1.13.1&new-version=1.15.1)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

Dependabot will **not** automatically merge this PR because it includes a minor update to a production dependency.

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

</details>
This was referenced Oct 15, 2018
Closed
Merged
Closed
This was referenced Jan 15, 2019
Closed
Closed
Closed
Merged
Merged
Closed
@dependabot-preview dependabot-preview bot mentioned this issue Jan 23, 2019
Merged
This was referenced Jun 4, 2019
Closed
Merged
@dependabot-preview dependabot-preview bot mentioned this issue Aug 20, 2019
Open
This was referenced Mar 10, 2021
Merged
Merged
Open
Open
Merged
Open
Open
Open
Merged
Merged
Merged
Open
Open
Open
Closed
Open
Merged
Closed
@dependabot dependabot bot mentioned this issue Mar 18, 2021
Open
@snyk-bot snyk-bot mentioned this issue May 4, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@melloc melloc

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@arekinath @melloc