Skip to content
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

Meterpreter Extension Base IDs #16267

Open
smcintyre-r7 opened this issue Mar 3, 2022 · 3 comments
Open

Meterpreter Extension Base IDs #16267

smcintyre-r7 opened this issue Mar 3, 2022 · 3 comments
Labels
breaking change Features that are great, but will cause breaking changes and should be deployed on a large release. confirmed Issues confirmed by a committer

Comments

@smcintyre-r7
Copy link
Contributor

Each Meterpreter defines it's own TLVs and each should be namespaced into their dedicated ranges. The sniffer and extapi extensions are both currently set to 0 which can create conflicts when determining the TLV types based on their numeric value.

The Python, Sniffer and Extapi extensions should be updated to have a unique extension base and their types should all take that into account. This is marked as a breaking change because it would alter the IDs that are used for communication between Metasploit and the Meterpreter instance.

@smcintyre-r7 smcintyre-r7 added the breaking change Features that are great, but will cause breaking changes and should be deployed on a large release. label Mar 3, 2022
@smcintyre-r7
Copy link
Contributor Author

The railgun types should also be updated to use the STDAPI extension base.

@adfoster-r7
Copy link
Contributor

Cross-referencing the initial issue that spawned this discussion #16258 (comment)

@github-actions
Copy link

github-actions bot commented Apr 4, 2022

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

@github-actions github-actions bot added the Stale Marks an issue as stale, to be closed if no action is taken label Apr 4, 2022
@adfoster-r7 adfoster-r7 added the confirmed Issues confirmed by a committer label Apr 4, 2022
@github-actions github-actions bot removed the Stale Marks an issue as stale, to be closed if no action is taken label Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change Features that are great, but will cause breaking changes and should be deployed on a large release. confirmed Issues confirmed by a committer
Projects
None yet
Development

No branches or pull requests

2 participants