Skip to content

Commit ab48123

Browse files
authored
Update cve.md (#9644)
* Update cve.md * Update cve.md
1 parent a1400df commit ab48123

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

release-notes/9.0/cve.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,14 @@
22

33
The .NET Team releases [monthly updates for .NET 9](https://github.com/dotnet/announcements/labels/.NET%209.0) on [Patch Tuesday](https://en.wikipedia.org/wiki/Patch_Tuesday). These updates often include security fixes. If you are on an older version, your app may be vulnerable.
44

5-
Your app needs to be on the latest .NET 8 patch version to be secure. The longer you wait to upgrade, the greater the exposure to CVEs.
5+
Your app needs to be on the latest .NET 9 patch version to be secure. The longer you wait to upgrade, the greater the exposure to CVEs.
66

77
## Which CVEs apply to my app?
88

99
Your app may be vulnerable to the following published security [CVEs](https://www.cve.org/) if you are using the given version or older.
1010

1111
- 9.0.0 (November 2024)
12-
- [CVE-2024-43498 | .NET Remote Code Execution Vulnerability](https://github.com/dotnet/announcements/issues/xxx)
13-
- [CVE-2024-43499 | .NET Denial of Service Vulnerability](https://github.com/dotnet/announcements/issues/xxx)
12+
- [CVE-2024-43498 | .NET Remote Code Execution Vulnerability](https://github.com/dotnet/announcements/issues/334)
13+
- [CVE-2024-43499 | .NET Denial of Service Vulnerability](https://github.com/dotnet/announcements/issues/333)
1414

1515
The CVE exposure is cumulative. For example, `8.0.0` users may be vulnerable to the CVEs present in `9.0.0` and newer releases. Similarly, `9.0.3` users may be vulnerable to the CVEs present in `9.0.4` and newer releases. The latest release is not vulnerable to any published CVEs.

0 commit comments

Comments
 (0)