Skip to content

πŸ›‘οΈ Sentinel: [CRITICAL] Fix Remote Code Execution in PDF generation#327

Open
anchapin wants to merge 1 commit into
mainfrom
sentinel-fix-pdf-rce-1243005084294333709
Open

πŸ›‘οΈ Sentinel: [CRITICAL] Fix Remote Code Execution in PDF generation#327
anchapin wants to merge 1 commit into
mainfrom
sentinel-fix-pdf-rce-1243005084294333709

Conversation

@anchapin
Copy link
Copy Markdown
Owner

🚨 Severity: CRITICAL
πŸ’‘ Vulnerability: Unsafe subprocess calls to LaTeX compilers (pdflatex, pandoc) permitted arbitrary shell command execution (\write18) if evaluating untrusted text. Subprocess calls lacked timeouts and explicit process cleanup, creating a potential Denial of Service (DoS) and zombie process vectors when encountering hanging or malicious LaTeX documents.
🎯 Impact: Allowed Remote Code Execution (RCE) on the server handling PDF compilation, potentially compromising entire systems.
πŸ”§ Fix: Added -no-shell-escape flags directly to pdflatex (-no-shell-escape) and pandoc (--pdf-engine-opt=-no-shell-escape) in cli/generators/cover_letter_generator.py and cli/pdf/converter.py. Added explicit timeouts (timeout=30) and process cleanup mechanisms (process.kill(), process.communicate()) to prevent zombies.
βœ… Verification: Verified by passing all test suites and specific security tests (test_pdf_security.py). Run bandit -r cli/ -x tests/ to confirm.


PR created automatically by Jules for task 1243005084294333709 started by @anchapin

Added `-no-shell-escape` flag to all `pdflatex` and `pandoc` subprocess
calls to prevent arbitrary command execution via `\write18` malicious
input. Implemented 30s timeouts and explicit process cleanup to prevent
infinite compilation loops (DoS vector).

Co-authored-by: anchapin <6326294+anchapin@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.

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @anchapin, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

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