Skip to content

setopt: refuse blobs with zero length#20705

Closed
bagder wants to merge 1 commit intomasterfrom
bagder/blob-no-len
Closed

setopt: refuse blobs with zero length#20705
bagder wants to merge 1 commit intomasterfrom
bagder/blob-no-len

Conversation

@bagder
Copy link
Member

@bagder bagder commented Feb 24, 2026

A blob must have a length or it will not be accepted. By enforcing the check here, TLS backend code can rely on the fact that the length is always non-zero from this point.

Reported-by: aisle-research-bot
URL: #20689 (review)

A blob must have a length or it will not be accepted. By enforcing the
check here, TLS backend code can rely on the fact that the length is
always non-zero from this point.

Reported-by: aisle-research-bot
URL: #20689 (review)
@bagder
Copy link
Member Author

bagder commented Feb 24, 2026

@aisle-analyzer

@aisle-research-bot
Copy link

aisle-research-bot bot commented Feb 24, 2026

🔒 Aisle Security Analysis

✅ We scanned this PR and did not find any security vulnerabilities.

Aisle supplements but does not replace security review.


Analyzed PR: #20705 at commit a61c812

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds validation to reject blobs with zero length in the Curl_setblobopt function. This prevents out-of-bounds memory access in TLS backend code (specifically mbedTLS) where code accesses blob->data[blob->len - 1] to check for null termination, which would cause undefined behavior if len is 0.

Changes:

  • Add zero-length validation check in Curl_setblobopt() to reject blobs with len equal to 0

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@bagder bagder closed this in 956e1ae Feb 24, 2026
@bagder bagder deleted the bagder/blob-no-len branch February 24, 2026 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants