Some users set an entity s children manually in the getEntity SAX callback to restrict entity expansion. This stopped working after renaming the checked member of xmlEntity, making at least one downstream project and its dependants susceptible to XXE attacks.
Some users set an entity schildren manually in the getEntity SAX callback to restrict entity expansion. This stopped working after renaming the checked member of xmlEntity, making at least one downstream project and its dependants susceptible to XXE attacks.
Some users set an entitys children manually in the getEntity SAX callback to restrict entity expansion. This stopped working after renaming the checked member of xmlEntity, making at least one downstream project and its dependantssusceptible to XXE attacks.
Some users set an entity s children manually in the getEntity SAX callback to restrict entity expansion. This stopped working after renaming the checked member of xmlEntity, making at least one downstream project and its dependants susceptible to XXE attacks.
Some users set an entity s children manually in the getEntity SAX callback to restrict entity expansion. This stopped working after renaming the checked member of xmlEntity, making at least one downstream project and its dependants susceptible to XXE attacks.
Some users set an entity schildren manually in the getEntity SAX callback to restrict entity expansion. This stopped working after renaming the checked member of xmlEntity, making at least one downstream project and its dependants susceptible to XXE attacks.
Some users set an entitys children manually in the getEntity SAX callback to restrict entity expansion. This stopped working after renaming the checked member of xmlEntity, making at least one downstream project and its dependantssusceptible to XXE attacks.