swagger-api / swagger-api/swagger-codegen

WS-2018-0111 (High) detected in base64-url-1.2.1.tgz

Open
#11,358 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

security vulnerability
Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

WS-2018-0111 - High Severity Vulnerability

Vulnerable Library - base64-url-1.2.1.tgz

Base64 encode, decode, escape and unescape for URL applications

Library home page: https://registry.npmjs.org/base64-url/-/base64-url-1.2.1.tgz

Path to dependency file: /samples/dynamic-html/package.json

Path to vulnerable library: /samples/dynamic-html/node_modules/base64-url/package.json

Dependency Hierarchy:

  • express-3.21.2.tgz (Root Library)
    • connect-2.30.2.tgz
      • express-session-1.11.3.tgz
        • uid-safe-2.0.0.tgz
          • base64-url-1.2.1.tgz (Vulnerable Library)

Found in HEAD commit: 4b7a8d7d7384aa6a27d6309c35ade0916edae7ed

Found in base branches: 3.0.0, master

Vulnerability Details

Versions of base64-url before 2.0.0 are vulnerable to out-of-bounds read as it allocates uninitialized Buffers when number is passed in input.

Publish Date: 2018-05-16

URL: WS-2018-0111

CVSS 3 Score Details (9.1)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: High
    • Integrity Impact: None
    • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://nodesecurity.io/advisories/660

Release Date: 2018-01-27

Fix Resolution (base64-url): 2.0.0

Direct dependency fix Resolution (express): 4.0.0


  • Check this box to open an automated fix PR

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with samples/dynamic-html/package.json and inspect how express-3.21.2 brings in the vulnerable base64-url dependency through express-session and uid-safe. Review the dependency tree and upgrade path, then verify that the resolved dependency is no longer base64-url 1.2.1 and that the dynamic-html sample still works.

Written by the indexing model from the issue text.

Assessment

Tech stack
express, node.js
Domain
backend, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.