Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1516 by [email protected]: Ses.UnsafeError should not be
accessible
http://code.google.com/p/google-caja/issues/detail?id=1516
What steps will reproduce the problem?
1. Initialize Ses
2. Evaluate Ses.UnsafeError
What is the expected output? What do you see instead?
You get a reference to the _unfrozen_ Error primordial. This should not be
accessible after Ses has initialized.
Quoth Mark Miller, "That's a good point about ses.UnsafeError. Really, that
shouldn't be accessible after initialization even to SES privileged code.
Please file this as a bug, though not a security hole."
