SwaggerUI supports displaying remote OpenAPI definitions through the ?url parameter. This enables robust demonstration capabilities on sites like petstore.swagger.io, editor.swagger.io, and similar sites, where users often want to see what their OpenAPI definitions would look like rendered.
However, this functionality may pose a risk for users who host their own SwaggerUI instances. In particular, including remote OpenAPI definitions opens a vector for phishing attacks by abusing the trusted names/domains of self-hosted instances.
Resolution:
We've made the decision to disable query parameters (#4872) by default starting with SwaggerUI version 4.1.3. Please update to this version when it becomes available (ETA: 2021 December). Users will still be able to be re-enable the options at their discretion. We'll continue to enable query parameters on the Swagger demo sites.
:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.
WS-2021-0461 - Medium Severity Vulnerability
Vulnerable Library - swagger-ui-dist-3.25.0.tgz
[![NPM version](https://badge.fury.io/js/swagger-ui-dist.svg)](http://badge.fury.io/js/swagger-ui-dist)
Library home page: https://registry.npmjs.org/swagger-ui-dist/-/swagger-ui-dist-3.25.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/swagger-ui-dist/package.json
Dependency Hierarchy: - swagger-ui-express-4.1.3.tgz (Root Library) - :x: **swagger-ui-dist-3.25.0.tgz** (Vulnerable Library)
Found in HEAD commit: 15b744adda384be966bd6bcc52d9830c8bab440a
Found in base branch: master
Vulnerability Details
SwaggerUI supports displaying remote OpenAPI definitions through the ?url parameter. This enables robust demonstration capabilities on sites like petstore.swagger.io, editor.swagger.io, and similar sites, where users often want to see what their OpenAPI definitions would look like rendered. However, this functionality may pose a risk for users who host their own SwaggerUI instances. In particular, including remote OpenAPI definitions opens a vector for phishing attacks by abusing the trusted names/domains of self-hosted instances. Resolution: We've made the decision to disable query parameters (#4872) by default starting with SwaggerUI version 4.1.3. Please update to this version when it becomes available (ETA: 2021 December). Users will still be able to be re-enable the options at their discretion. We'll continue to enable query parameters on the Swagger demo sites.
Publish Date: 2021-12-09
URL: WS-2021-0461
CVSS 3 Score Details (6.1)
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: https://github.com/advisories/GHSA-qrmm-w75w-3wpx
Release Date: 2021-12-09
Fix Resolution (swagger-ui-dist): 4.1.3
Direct dependency fix Resolution (swagger-ui-express): 4.2.0
Step up your Open Source Security Game with Mend here