rbhanda commented 2 months ago

Microsoft Security Advisory CVE-2024-38167 | .NET Information Disclosure Vulnerability

Executive summary

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 8.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

A vulnerability exists in .NET runtime TlsStream which may result in Information Disclosure.

Announcement

Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/319

Mitigation factors

Microsoft has not identified any mitigating factors for this vulnerability.

Affected software

Any .NET 8.0 application running on .NET 8.0.7 or earlier.

Affected Packages

The vulnerability affects any Microsoft .NET Core project if it uses any of affected packages versions listed below

.NET 8

Package name	Affected version	Patched version
Microsoft.NetCore.App.Runtime.linux-arm	>= 8.0.0, < 8.0.8	8.0.8
Microsoft.NetCore.App.Runtime.linux-arm64	>= 8.0.0, < 8.0.8	8.0.8
Microsoft.NetCore.App.Runtime.linux-musl-arm	>= 8.0.0, < 8.0.8	8.0.8
Microsoft.NetCore.App.Runtime.linux-musl-arm64	>= 8.0.0, < 8.0.8	8.0.8
Microsoft.NetCore.App.Runtime.linux-musl-x64	>= 8.0.0, < 8.0.8	8.0.8
Microsoft.NetCore.App.Runtime.linux-x64	>= 8.0.0, < 8.0.8	8.0.8
Microsoft.NetCore.App.Runtime.osx-arm64	>= 8.0.0, < 8.0.8	8.0.8
Microsoft.NetCore.App.Runtime.osx-x64	>= 8.0.0, < 8.0.8	8.0.8
Microsoft.NetCore.App.Runtime.win-arm	>= 8.0.0, < 8.0.8	8.0.8
Microsoft.NetCore.App.Runtime.win-arm64	>= 8.0.0, < 8.0.8	8.0.8
Microsoft.NetCore.App.Runtime.win-x64	>= 8.0.0, < 8.0.8	8.0.8
Microsoft.NetCore.App.Runtime.win-x86	>= 8.0.0, < 8.0.8	8.0.8

Advisory FAQ

How do I know if I am affected?

If you have a runtime or SDK with a version listed, or an affected package listed in affected software or affected packages, you're exposed to the vulnerability.

How do I fix the issue?

To fix the issue please install the latest version of .NET 8.0 or .NET 6.0. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs.
If you have .NET 6.0 or greater installed, you can list the versions you have installed by running the dotnet --info command. You will see output like the following;

.NET Core SDK (reflecting any global.json):

 Version:   8.0.200
 Commit:    8473146e7d

Runtime Environment:

 OS Name:     Windows
 OS Version:  10.0.18363
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\6.0.300\

Host (useful for support):

  Version: 8.0.3
  Commit:  8473146e7d

.NET Core SDKs installed:

  8.0.200 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:

  Microsoft.AspAspNetCore.App 8.0.3 [C:\Program Files\dotnet\shared\Microsoft.AspAspNetCore.App]
  Microsoft.AspNetCore.App 8.0.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.WindowsDesktop.App 8.0.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

If you're using .NET 8.0, you should download and install .NET 8.0.8 Runtime or .NET 8.0.108 SDK (for Visual Studio 2022 v17.8) from https://dotnet.microsoft.com/download/dotnet-core/8.0.

.NET 8.0 updates are also available from Microsoft Update. To access this either type "Check for updates" in your Windows search, or open Settings, choose Update & Security and then click Check for Updates.

Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.

Additionally, if you've deployed self-contained applications targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.

Other Information

Reporting Security Issues

If you have found a potential security issue in .NET 8.0 or .NET 6.0, please email details to secure@microsoft.com. Reports may qualify for the Microsoft .NET Core & .NET 5 Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.

Support

You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime and https://github.com/dotnet/aspnet/. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.

Disclaimer

The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

Acknowledgement

We would like to thank Alex Appleton, D. E. Shaw & Co., L.P for reporting this vulnerability.

External Links

CVE-2024-38167

Revisions

V1.0 (October 02, 2024): Added missed acknowlegdement. V1.0 (August 13, 2024): Advisory published.

Version 1.1

Last Updated 2024-10-02

dotnet-policy-service[bot] commented 2 months ago

Tagging subscribers to this area: @dotnet/area-meta See info in area-owners.md if you want to be subscribed.

teo-tsirpanis commented 2 months ago

TlsStream is an internal class. Judging from its uses in the BCL, it should say FtpWebRequest and SmtpClient.

colejohnson66 commented 2 months ago

What is the actual vulnerability here? "[...] may result in Information Disclosure" doesn't provide any information on knowing if one could be affected.

wischi-chr commented 1 month ago

Is it possible that this change caused that issue: https://github.com/npgsql/npgsql/issues/5813 ?

Authentication failed because the remote party sent a TLS alert: 'InternalError'

Disable creation of stateful TLS session tickets by OpenSSL (Daniel Gustafsson) This avoids possible failures with clients that think receipt of a session ticket means that TLS session resumption is supported. https://github.com/npgsql/npgsql/issues/5813#issuecomment-2323994880

PS: Our application that fails is hosted on Azure AppServices so there isn't even a simple way (if any?) to roll back to a different runtime version

vonzshik commented 1 month ago

@wischi-chr it looks like it's a postgres bug (whether it exposes a .NET or windows bug is a different thing altogether). So at the very least it seems unlikely that this change affected npgsql.

dotnet / runtime