-
Notifications
You must be signed in to change notification settings - Fork 112
fix: block behavior gadgets in loose XAML #3048
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.
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
Open
lhx077
wants to merge
1
commit into
dev
Choose a base branch
from
codex/assess-wpf-behaviors-vulnerability
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+95
−5
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚨 issue (security): 基于值的类型检查可能会漏掉通过全限定名或标记扩展语法引用的危险类型。
ValidateLooseXamlValue只把value和disallowedType.Name做比较,因此像System.Diagnostics.Process、{x:Type Process}或其他带命名空间/标记形式的输入不会被拦截。如果这个检查是作为字符串值的安全兜底机制,建议至少使用EndsWith(disallowedType.Name, StringComparison.Ordinal),或者在比较前对常见模式做归一化处理,避免危险类型通过限定名或标记语法绕过过滤。Original comment in English
🚨 issue (security): The value-based type check may miss dangerous types referenced via fully qualified or markup-extension syntax.
ValidateLooseXamlValuecomparesvalueonly todisallowedType.Name, so inputs likeSystem.Diagnostics.Process,{x:Type Process}, or other namespace/markup forms will not be caught. If this check is intended as a safety net for string-only values, consider at least usingEndsWith(disallowedType.Name, StringComparison.Ordinal)or normalizing common patterns before comparison so dangerous types cannot bypass the filter via qualified or markup syntax.