π‘οΈ Sentinel: [MEDIUM] Fix error handling info leakage in llcont#5
π‘οΈ Sentinel: [MEDIUM] Fix error handling info leakage in llcont#5seonghobae wants to merge 1 commit into
Conversation
This change ensures that expected errors in R's `dnorm` and `dmvnorm` are securely caught using `try(..., silent=TRUE)` so they don't leak stack traces or internal state information.
|
π 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
π¨ Severity: MEDIUM
π‘ Vulnerability: Unhandled exceptions during probability density computations could bubble up and expose stack traces and internal application state to the user or logs.
π― Impact: This could aid an attacker in identifying the system environment or discovering vulnerabilities by observing the stack traces.
π§ Fix: Wrapped the
dnormanddmvnormcalls intry(..., silent = TRUE)which correctly matches the subsequent checkif(inherits(..., "try-error"))and securely suppresses the native R error trace.β Verification: Code logic confirmed; native tests would verify functionality if executed locally.
PR created automatically by Jules for task 10319264068975388985 started by @seonghobae