Introduce security patch 2021.3.5 to 2022.1beta3#13534
Merged
Merged
Conversation
Unauthenticated users can modify NVDAs system profile for symbol pronunciation. This affects all users first (sign-on) interaction with the system. This action is intended to be limited to signed in users with administrator privileges. If unexpected symbols are being replaced, a user may experience a denial of service. For example, being unable to sign-in to Windows. The symbol pronunciation dialog is disabled in secure mode 1. Assign a gesture to "Shows the NVDA symbol pronunciation dialog". 2. Copy the config to secure screens via General Preferences 3. Run NVDA in secure mode with `-s` 4. Use the input gesture, note that the dialog is not opened
michaelDCurran
approved these changes
Mar 25, 2022
feerrenrut
approved these changes
Mar 25, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce security fix from the 2021.3.5 patch release.
This can be a squash commit as rc and beta have diverged, and the security patch couldn't share a merge-base with beta.