|Index > Community > Security Reports||User List | Dev List | Wiki | Issue Tracker|
Please note that, except in rare circumstances, binary patches are not produced for individual vulnerabilities. To obtain the binary fix for a particular vulnerability you should upgrade to an Apache Geronimo build or release where that vulnerability has been fixed.
Source patches, usually in the form of JIRA references to SVN commits, may be provided in either in a vulnerability announcement and/or the vulnerability details listed on these pages. These source patches may be used by users wishing to build their own local version of Geronimo with just that security patch rather than upgrade.
Lists of security problems fixed in released versions of Apache Geronimo are available:
The Apache Software Foundation takes a very active stance in eliminating security problems and denial of service attacks against Apache Geronimo.
We strongly encourage folks to report such problems to our private security mailing list email@example.com first, before disclosing them in a public forum.
Please note that the security mailing list should only be used for reporting undisclosed security vulnerabilities in Apache Geronimo and managing the process of fixing such vulnerabilities. We cannot accept regular bug reports or other queries at this address. All mail sent to this address that does not relate to an undisclosed security problem in the Apache Geronimo source code will be ignored.
If you need to report a bug that isn't an undisclosed security vulnerability, please use the bug reporting page.
should be address to the users mailing list. Please see the mailing lists page for details of how to subscribe.
The private security mailing address is: firstname.lastname@example.org
Please report any errors or omissions to email@example.com