/* * Copyright (c) 2007, 2010, Oracle and/or its affiliates. All rights reserved. * ORACLE PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. * * * * * * * * * * * * * * * * * * * * */ package javax.xml.bind; import java.awt.*; import java.security.BasicPermission; /** * This class is for JAXB permissions. A {@code JAXBPermission} * contains a name (also referred to as a "target name") but * no actions list; you either have the named permission * or you don't. * *
* The target name is the name of the JAXB permission (see below). * *
* The following table lists all the possible {@code JAXBPermission} target names, * and for each provides a description of what the permission allows * and a discussion of the risks of granting code the permission. *
* *
Permission Target Name | *What the Permission Allows | *Risks of Allowing this Permission | *
---|---|---|
setDatatypeConverter | ** Allows the code to set VM-wide {@link DatatypeConverterInterface} * via {@link DatatypeConverter#setDatatypeConverter(DatatypeConverterInterface) the setDatatypeConverter method} * that all the methods on {@link DatatypeConverter} uses. * | ** Malicious code can set {@link DatatypeConverterInterface}, which has * VM-wide singleton semantics, before a genuine JAXB implementation sets one. * This allows malicious code to gain access to objects that it may otherwise * not have access to, such as {@link Frame#getFrames()} that belongs to * another application running in the same JVM. * | *