Skip to content

AjpProcessor: fix readMessage() bounds check - #916

Merged
rmaucher merged 1 commit into
apache:mainfrom
MegaManSec:2
Nov 3, 2025
Merged

rmaucher merged 1 commit into
apache:mainfrom
MegaManSec:2

Conversation

@MegaManSec

Copy link
Copy Markdown
Contributor

The payload capacity should have been (buf.length - H_SIZE).

The payload capacity should have been (buf.length - H_SIZE).

Signed-off-by: Joshua Rogers <MegaManSec@users.noreply.github.com>
@rmaucher
rmaucher merged commit d3968c5 into apache:main Nov 3, 2025
@MegaManSec

Copy link
Copy Markdown
Contributor Author

@rmaucher java is not my area of exptertise. what's the actual outcome of this bug? it was found automatically with ZeroPath, btw.

@rmaucher

rmaucher commented Nov 3, 2025

Copy link
Copy Markdown
Contributor

That makes sense so it was merged.

@MegaManSec

MegaManSec commented Nov 3, 2025 •

Copy link
Copy Markdown
Contributor Author

sorry, i mean, what could this bug actually cause? just some type of exception e.g. ArrayIndexOutOfBoundsException?

@rmaucher

rmaucher commented Nov 3, 2025

Copy link
Copy Markdown
Contributor

The error is supposed to be reported with a specific message, and this would instead be an array out of bounds exception, but there's nothing very significant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants