libgcj/10597: core classes must not have observable synchronization

tromey@redhat.com tromey@redhat.com
Fri May 2 04:16:00 GMT 2003


>Number:         10597
>Category:       libgcj
>Synopsis:       core classes must not have observable synchronization
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri May 02 04:16:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Tom Tromey
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
Some of our core classes, like String, acquire the 
class lock.  This means a malicious program could
prevent certain operations by acquiring one of these
locks and never releasing it.

Critical core classes should never acquire their class
lock, but should instead use some inaccessible object.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the Java-prs mailing list