fix(security): disable reading config params from URL search params (#7697)
Reading configuration parameters from URL search params is by default no longer enabled. To re-enable it, set queryConfigEnabled configuration parameter to true. Functionally, this is a breaking change, but given we're just providing a security vulnerability patch we're considering this a PATCH version bump only. Refs #4872 Refs https://github.com/swagger-api/swagger-ui/security/advisories/GHSA-qrmm-w75w-3wpx
This commit is contained in:
@@ -77,6 +77,7 @@ export default function SwaggerUI(opts) {
|
||||
"patch",
|
||||
"trace"
|
||||
],
|
||||
queryConfigEnabled: false,
|
||||
|
||||
// Initial set of plugins ( TODO rename this, or refactor - we don't need presets _and_ plugins. Its just there for performance.
|
||||
// Instead, we can compile the first plugin ( it can be a collection of plugins ), then batch the rest.
|
||||
@@ -108,7 +109,7 @@ export default function SwaggerUI(opts) {
|
||||
}
|
||||
}
|
||||
|
||||
let queryConfig = parseSearch()
|
||||
let queryConfig = opts.queryConfigEnabled ? parseSearch() : {}
|
||||
|
||||
const domNode = opts.domNode
|
||||
delete opts.domNode
|
||||
|
||||
Reference in New Issue
Block a user