Handle Exceptions during Intent parsing logic to avoid DoS on Android #472
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
balazsgerlei
force-pushed
the
handle-exceptions-during-intent-parsing
branch
2 times, most recently
from
84be7f8 to
119e9ca
Compare
balazsgerlei
changed the title
balazsgerlei
force-pushed
the
handle-exceptions-during-intent-parsing
branch
from
119e9ca to
ee81d7a
Compare
… Android - Putting a custom Serializable class into an Intent sent to MainActivity of the Android app could cause a crash, which is easily avoidable with a try-catch
balazsgerlei
force-pushed
the
handle-exceptions-during-intent-parsing
branch
from
ee81d7a to
487c5de
Compare
zsmb13
approved these changes
Nov 3, 2025
auto-merge was automatically disabled
November 3, 2025 12:37
Pull request was converted to draft
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Putting a custom
Serializableclass into an Intent sent toMainActivityof the Android app could cause a crash, which is easily avoidable with a try-catch.My IntentFuzzer app can be used for reproduction: after finding the KotlinConf 2025 app in the list of Non-System Apps, a long-press on the
MainActivitycomponent sends anIntentwith a custom class (only known by the IntentFuzzer app) that isSerializableinextraswhich would cause aRuntimeExceptioncaused byClassNotFoundExceptionin theprocessIntentlogic ofMainActivity.