Skip to content

Remove stack trace printing to prevent info exposure#15

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

Remove stack trace printing to prevent info exposure#15
victor-nb wants to merge 1 commit intomainfrom
boost-advisor/fix-9BGymWGP

Conversation

@victor-nb
Copy link
Copy Markdown

Summary

This PR fixes 1 security vulnerability identified by BoostSecurity.


Remove stack trace printing in RecosEdgeProcessor in src/scala/com/twitter/recos/hose/common/RecosEdgeProcessor.scala (Line: 36)

Risk: Exception.printStackTrace() in RecosEdgeProcessor could expose internal class names, file paths, and line numbers via stderr, enabling information disclosure (CWE-209).

Fix: Removed the printStackTrace() call and retained error accounting via the existing process_errors counter while returning Future.Unit as before.

Review notes: This reduces diagnostic output on failures; monitoring should rely on the error counter/metrics rather than stderr stack traces.


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