Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MsQuic needs to use zero-initialized pool by default #4870

Open
3 of 4 tasks
mtfriesen opened this issue Feb 27, 2025 · 0 comments
Open
3 of 4 tasks

MsQuic needs to use zero-initialized pool by default #4870

mtfriesen opened this issue Feb 27, 2025 · 0 comments
Labels
Area: Security Related to security or quality testing
Milestone
Future

Comments

@mtfriesen
Copy link
Contributor

Describe the bug

Windows requires zero-initialized pool allocations by default, with uninitialized allocations explicitly opt-in on a case-by-case basis. MsQuic should conform with these security requirements.

Affected OS

  • Windows
  • Linux
  • macOS
  • Other (specify below)

Additional OS information

No response

MsQuic version

main

Steps taken to reproduce bug

Use CxPlatProcessorInfo variable to interact with OS.

Expected behavior

The OS accepts the CxPlatProcessorInfo as valid parameters.

Actual outcome

The OS rejects CxPlatProcessorInfo because the PADDING field, which maps to the OS Reserved field, is not zero.

Additional details

No response
@mtfriesen mtfriesen added the Area: Security Related to security or quality testing label Feb 27, 2025
@nibanks nibanks added this to the Future milestone Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area: Security Related to security or quality testing
Projects
DPT Iteration Tracker
Status: No status
Milestone
Future
Development

No branches or pull requests
2 participants
@mtfriesen @nibanks