[CVE-2020-9492] Apache Hadoop Potential privilege escalation

                							

                <!--X-Body-Begin-->
<!--X-User-Header-->

oss-sec
mailing list archives
<!--X-User-Header-End-->
<!--X-TopPNI-->

By Date

By Thread

</form>

<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
[CVE-2020-9492] Apache Hadoop Potential privilege escalation

<!--X-Subject-Header-End-->
<!--X-Head-of-Message-->

From: Akira Ajisaka &lt;aajisaka () apache org&gt;

Date: Tue, 26 Jan 2021 09:34:07 +0900

<!--X-Head-of-Message-End-->
<!--X-Head-Body-Sep-Begin-->

<!--X-Head-Body-Sep-End-->
<!--X-Body-of-Message-->
CVE-2020-9492. Apache Hadoop Potential privilege escalation

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected:
3.2.0 to 3.2.1, 3.0.0-alpha1 to 3.1.3, 2.0.0-alpha to 2.10.0

Description:
WebHDFS client might send SPNEGO authorization header to remote URL
without proper verification. A crafty user can trigger services to
send server credentials to a webhdfs path for capturing the service
principal.

Mitigation:
Users of the affected versions should apply either of the following mitigations:
- Set different http signature secrets and use dedicated hosts for
each privileged impersonation service (such as HiveServer2).
- Upgrade to 3.3.0, 3.2.2, 3.1.4, 2.10.1, or newer with TLS encryption
enabled and configure dfs.http.policy to HTTPS_ONLY.

Credit:
This issue was discovered by Kevin Risden.

<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->

<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->

By Date

By Thread

Current thread:

[CVE-2020-9492] Apache Hadoop Potential privilege escalation Akira Ajisaka (Jan 26)

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->