Skip to content

fix(security): [HIGH] resolve uncontrolled memory consumption DoS in automaton builder#174

Open
Tugamer89 wants to merge 1 commit into
mainfrom
fix-builder-state-explosion-14210009594660108661
Open

fix(security): [HIGH] resolve uncontrolled memory consumption DoS in automaton builder#174
Tugamer89 wants to merge 1 commit into
mainfrom
fix-builder-state-explosion-14210009594660108661

Conversation

@Tugamer89

Copy link
Copy Markdown
Owner

Severity: HIGH
Vulnerability: Unbounded state creation in AbstractAutomatonBuilder allows manual automaton construction loops to consume arbitrary amounts of memory, potentially leading to a Denial-of-Service (DoS) condition via OutOfMemoryError or IllegalStateException on JVM memory exhaustion.
Impact: An attacker supplying malicious input to code paths that dynamically construct automata via the public builder API could crash the application by intentionally triggering an infinite state creation loop.
Fix: Implemented a hard limit (MAX_STATES = 10000) within AbstractAutomatonBuilder#addState. If this limit is exceeded when attempting to add a new state, an IllegalStateException is thrown, securely terminating the operation before memory is exhausted.
Verification: Added AbstractAutomatonBuilderSecurityTest which iteratively adds 10,000 states and verifies that attempting to add the 10,001st state correctly throws an IllegalStateException. Tested manually with mvn test.


PR created automatically by Jules for task 14210009594660108661 started by @Tugamer89

- Added a `MAX_STATES` limit to `AbstractAutomatonBuilder.java` to prevent
  infinite state creation loops from exhausting memory during manual
  automaton construction.
- Created `AbstractAutomatonBuilderSecurityTest.java` to verify the DoS
  prevention logic.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@sonarqubecloud

Copy link
Copy Markdown

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.

1 participant