Skip to content

Remove stack trace printing to prevent information exposure#4

Open
victor-nb wants to merge 1 commit intomainfrom
boost-advisor/fix-rqnUJu8z
Open

Remove stack trace printing to prevent information exposure#4
victor-nb wants to merge 1 commit intomainfrom
boost-advisor/fix-rqnUJu8z

Conversation

@victor-nb
Copy link
Copy Markdown

Summary

This PR fixes 1 security vulnerability identified by BoostSecurity.


Remove printStackTrace to prevent info exposure in src/scala/com/twitter/recos/hose/common/RecosEdgeProcessor.scala (Line: 36)

Risk: Throwable.printStackTrace() wrote full stack traces to stderr, exposing internal class/method names, file paths, and potentially sensitive data (CWE-209).

Fix: Removed printStackTrace() from RecosEdgeProcessor and replaced it with error metrics (including a per-exception-type counter) to retain observability without leaking implementation details.

Review notes: Error handling behavior remains non-failing (Future.Unit), but stack traces will no longer be emitted to stderr.


Generated by BoostSecurity Advisor

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