dotnet7.0-7.0.119-1.fc39

Read Time:20 Second

FEDORA-2024-3136a71490

Packages in this update:

dotnet7.0-7.0.119-1.fc39

Update description:

This is the May 2024 security update for .NET 7.

This is the last upstream release of .NET 7. After this update, .NET 7 reaches its End of Life (EOL).

Full release notes: https://github.com/dotnet/core/blob/main/release-notes/7.0/7.0.19/7.0.19.md

Read More

USN-6773-1: .NET vulnerabilities

Read Time:20 Second

It was discovered that .NET did not properly handle memory in it’s
Double Parse routine. An attacker could possibly use this issue to
achieve remote code execution. (CVE-2024-30045)

It was discovered that .NET did not properly handle the usage of a
shared resource. An attacker could possibly use this to cause a dead-lock
condition, resulting in a denial of service. (CVE-2024-30046)

Read More

Zero-Trust DNS

Read Time:1 Minute, 9 Second

Microsoft is working on a promising-looking protocol to lock down DNS.

ZTDNS aims to solve this decades-old problem by integrating the Windows DNS engine with the Windows Filtering Platform—the core component of the Windows Firewall—directly into client devices.

Jake Williams, VP of research and development at consultancy Hunter Strategy, said the union of these previously disparate engines would allow updates to be made to the Windows firewall on a per-domain name basis. The result, he said, is a mechanism that allows organizations to, in essence, tell clients “only use our DNS server, that uses TLS, and will only resolve certain domains.” Microsoft calls this DNS server or servers the “protective DNS server.”

By default, the firewall will deny resolutions to all domains except those enumerated in allow lists. A separate allow list will contain IP address subnets that clients need to run authorized software. Key to making this work at scale inside an organization with rapidly changing needs. Networking security expert Royce Williams (no relation to Jake Williams) called this a “sort of a bidirectional API for the firewall layer, so you can both trigger firewall actions (by input *to* the firewall), and trigger external actions based on firewall state (output *from* the firewall). So instead of having to reinvent the firewall wheel if you are an AV vendor or whatever, you just hook into WFP.”

Read More