Skip to content

🛡️ Sentinel: [CRITICAL] Fix pdflatex RCE and DoS mitigation in PDF compilation#375

Open
anchapin wants to merge 1 commit into
mainfrom
sentinel/fix-pdflatex-rce-and-dos-mitigation-5904571803552083737
Open

🛡️ Sentinel: [CRITICAL] Fix pdflatex RCE and DoS mitigation in PDF compilation#375
anchapin wants to merge 1 commit into
mainfrom
sentinel/fix-pdflatex-rce-and-dos-mitigation-5904571803552083737

Conversation

@anchapin

Copy link
Copy Markdown
Owner

🚨 Severity: CRITICAL

💡 Vulnerability:
The PDF compilation functions in cli/pdf/converter.py and cli/generators/cover_letter_generator.py executed pdflatex and pandoc without strict sandboxing (-no-shell-escape) and without timeouts in their subprocess.communicate() calls.

🎯 Impact:

  • Remote Code Execution (RCE): Malicious user input or AI-hallucinated LaTeX control macros (e.g., \write18{...}) could execute arbitrary shell commands on the host system because LaTeX shells are permitted by default.
  • Denial of Service (DoS): Without a timeout on communicate(), maliciously crafted .tex files designed to loop infinitely could hang the compilation process indefinitely, leading to resource exhaustion.

🔧 Fix:

  • Appended the -no-shell-escape flag to the primary pdflatex calls and --pdf-engine-opt=-no-shell-escape to the fallback pandoc calls.
  • Implemented a 30-second timeout on all subprocess.communicate() calls, gracefully catching subprocess.TimeoutExpired, terminating the hung process (kill()), clearing the buffers, and returning False without raising unhandled exceptions or halting application flow.

Verification:

  • Extensive timeout and argument unit tests were added to tests/test_pdf_security.py to ensure complete coverage of both PDFConverter and CoverLetterGenerator implementations.
  • All format, lint, and core tests passed securely.

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

@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.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

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