Add additional port 6835/tcp to Apache ActiveMQ OpenWire Transport detection #11237
+3
−3
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.
PR Information
This PR adds port
6835/tcp
to the detection of Apache ActiveMQ OpenWire Transport services.Additionally, it improves the regex to use an arbitrary number of whitespace characters between(Update: I've reverted this optimization, connecting to an actual ActiveMQ port showed that we indeed have to match three bytesProviderVersion
and the version number.\t\x00\x06
).Typically, the service runs on port
61616/tcp
. However, during three independent penetration tests I've seen the service run on6835/tcp
, over which I was able to successfully exploit CVE-2023-46604.This PR assumes that PR #4401 works as intended.
Template Validation
I've validated this template locally?
Using a mock service (since I currently don't have access to an ActiveMQ instance), the detection seems to work as intended:Update: I've verified this template with ActiveMQ 5.15.6:
Additional Details
I've observed the following patterns during my penetration tests: