Potential fix for code scanning alert no. 10: String length conflation - #756
Merged
Conversation
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
tianjianjiang
marked this pull request as ready for review
December 5, 2025 07:50
|
Persistent review updated to latest commit a211050 |
lukhnos
requested changes
Dec 5, 2025
lukhnos
left a comment
Contributor
There was a problem hiding this comment.
Let's take the Copilot's suggestion, i.e. replace composingBuffer.count with composingBuffer.utf16.count, which is the correct idiomatic fix here.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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
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.
User description
Potential fix for https://github.com/openvanilla/McBopomofo/security/code-scanning/10
To fix the problem, ensure that all offsets and lengths passed to NSRange (such as in
NSMakeRange) are expressed in UTF-16 code units as expected by NSString and Cocoa APIs. Specifically, instead of usingcomposingBuffer.count, use the length of the corresponding NSString, i.e.NSString(string: composingBuffer).length.File/region to change:
Update the
selectionRange: NSMakeRange(composingBuffer.count, 0)to use the NSString length instead.No new methods or complex imports are required; NSString is available via Foundation/Cocoa.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.
PR Type
Bug fix
Description
Fix UTF-16 length for NSRange
Prevent string length conflation issue
Align selectionRange with Cocoa expectations
Diagram Walkthrough
File Walkthrough
InputMethodController.swift
Use NSString length for NSRange in setMarkedTextSource/InputMethodController.swift