[Security] Bump undertow-core from 2.0.13.Final to 2.1.1.Final

dependabot-preview[bot] commented 3 years ago

Bumps undertow-core from 2.0.13.Final to 2.1.1.Final. This update includes security fixes.

Vulnerabilities fixed

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects io.undertow:undertow-core undertow before version 2.0.23.Final is vulnerable to an information leak issue. Web apps may have their directory structures predicted through requests without trailing slashes via the api.

Affected versions: < 2.0.23

Sourced from The GitHub Security Advisory Database.

High severity vulnerability that affects io.undertow:undertow-core A flaw was found in, all under 2.0.20, in the Undertow DEBUG log for io.undertow.request.security. If enabled, an attacker could abuse this flaw to obtain the user's credentials from the log files.

Affected versions: < 2.0.20

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects io.undertow:undertow-core A vulnerability was found in Undertow web server before 2.0.21. An information exposure of plain text credentials through log files because Connectors.executeRootHandler:402 logs the HttpServerExchange object at ERROR level using UndertowLogger.REQUEST_LOGGER.undertowRequestFailed(t, exchange)

Affected versions: < 2.0.21

Sourced from The GitHub Security Advisory Database.

Improper Restriction of Operations within the Bounds of a Memory Buffer in Undertow A flaw was discovered in Undertow in versions before Undertow 2.1.1.Final where certain requests to the "Expect: 100-continue" header may cause an out of memory error. This flaw may potentially lead to a denial of service.

Affected versions: <= 2.1.0.Final

Sourced from The GitHub Security Advisory Database.

HTTP Request Smuggling in Undertow A flaw was found in Undertow in versions before 2.1.1.Final, regarding the processing of invalid HTTP requests with large chunk sizes. This flaw allows an attacker to take advantage of HTTP request smuggling.

Affected versions: <= 2.1.0.Final

Sourced from The GitHub Security Advisory Database.

HTTP Request Smuggling in Undertow A flaw was discovered in all versions of Undertow before Undertow 2.2.0.Final, where HTTP request smuggling related to CVE-2017-2666 is possible against HTTP/1.x and HTTP/2 due to permitting invalid characters in an HTTP request. This flaw allows an attacker to poison a web-cache, perform an XSS attack, or obtain sensitive information from request other than their own.

Affected versions: <= 2.1.0.Final

Sourced from The GitHub Security Advisory Database.

HTTP request smuggling in Undertow A flaw was found in Undertow. A regression in the fix for CVE-2020-10687 was found. HTTP request smuggling related to CVE-2017-2666 is possible against HTTP/1.x and HTTP/2 due to permitting invalid characters in an HTTP request. This flaw allows an attacker to poison a web-cache, perform an XSS attack, or obtain sensitive information from request other than their own. The highest threat from this vulnerability is to data confidentiality and integrity.

Affected versions: < 2.0.34

Commits

466e2b0 Prepare 2.1.1.Final
38d577d Merge pull request #890 from fl4via/UNDERTOW-1706
c74b8ff Merge pull request #889 from spyrkob/UNDERTOW-1657
30b029f [UNDERTOW-1709][JBEAP-19266] NullPointerException when calling the AJP port w...
daea64d [UNDERTOW-1706] Fix issue with wildfly-common dependency and maven enforcer r...
b5e03e5 Merge pull request #880 from stuartwdouglas/UNDERTOW-1197
6dd4bb9 Merge pull request #888 from spyrkob/UNDERTOW-1708
28739ef Merge pull request #887 from hyperxpro/master
6da9ecc [UNDERTOW-1710] Update pom.xml
7d69c35 Merge pull request #886 from fl4via/UNDERTOW-1419
Additional commits viewable in compare view

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 commands and options

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 squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor 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) - 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)