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

fix error handling in blacklist processing #1916

Closed
wants to merge 2 commits into from
Closed

fix error handling in blacklist processing #1916

wants to merge 2 commits into from

Conversation

cxmplex
Copy link

@cxmplex cxmplex commented May 22, 2024

Currently, if attackers are able to cause an error in the blacklist function, as they can with the current subnet example code, this error will propagate downstream to here.

Please see my associated PR in the subnet example repository that addresses the default code having an exploitable line to force an error:

opentensor/bittensor-subnet-template#88

@cxmplex cxmplex changed the title fix major vulnerability in blacklist processing fix vulnerability in blacklist processing May 22, 2024
@cxmplex cxmplex changed the title fix vulnerability in blacklist processing fix vulnerability in blacklist processing / blacklist bypass vulnerability May 22, 2024
@cxmplex cxmplex changed the title fix vulnerability in blacklist processing / blacklist bypass vulnerability fix vulnerability in blacklist processing / blacklist bypass exploit May 22, 2024
@cxmplex cxmplex changed the title fix vulnerability in blacklist processing / blacklist bypass exploit blacklist bypass exploit | fix vulnerability in blacklist processing May 22, 2024
@cxmplex cxmplex changed the title blacklist bypass exploit | fix vulnerability in blacklist processing fix error handling in blacklist processing May 22, 2024
@cxmplex
Copy link
Author

cxmplex commented May 22, 2024

Spoke with upstream devs about this as its more appropriate to fix it on SN side as it doesnt appear any function in part of the axon operation has its exceptions caught. this likely means the onus is on the sn dev to catch them and the existing pattern should not be modified. As a result, PR closed.

@cxmplex cxmplex closed this May 22, 2024
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.

None yet

1 participant