Potential sensitive information leak through JVM crash logs

[Thomas Stüfe]

On Sat, Jan 14, 2023 at 11:39 AM Alexandr Miloslavskiy <
alexandr.miloslavskiy at syntevo.com> wrote:

> Hi,
>
> > A simple way to deal with this could be to mark error reporting steps
> > that potentially display security-sensitive information. See VM::report,
> > STEP macro.
> >
> > These steps could print a little prefix/suffix for strippers to do their
> > work.
>
> Unfortunately this won't help, because we don't want to strip entire
> sections that might contain sensitive information.
>
> For debugging purposes, the contents of registers and stack values are
> quite important. At the same time, we consider these values unlikely to
> disclose any sensitive information.
>
>
Sure, but registers may contain parts of a string, e.g. when processing
strings, or accidentally reading from text. How do you want to prevent
that, or do you consider unlikely enough to live with it?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-dev/attachments/20230114/8d8b4c41/attachment.htm>