Reporting New Security Problems with Apache Sling¶
The Apache Software Foundation takes a very active stance in eliminating security problems and denial of service attacks against Apache Sling.
We strongly encourage folks to report such problems to our private security mailing list 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 Sling 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 Sling source code will be ignored.
If you need to report a bug that isn't an undisclosed security vulnerability, please use our public issue tracker.
- how to configure Sling securely
- whether a published vulnerability applies to your particular application
- obtaining further information on a published vulnerability
- availability of patches and/or new releases
should be addressed to our public users mailing list. Please see the Project Information page for details of how to subscribe.
The private security mailing address is: security(at)sling.apache.org.
Note that all networked servers are subject to denial of service attacks, and we cannot promise magic workarounds to generic problems (such as a client streaming lots of data to your server, or re-requesting the same URL repeatedly). In general our philosophy is to avoid any attacks which can cause the server to consume resources in a non-linear relationship to the size of inputs.
Errors and omissions¶
Please report any errors or omissions to security(at)sling.apache.org.
Previously reported security issues¶
- CVE-2012-2138 - Apache Sling denial of service vulnerability (July 6th, 2012), see http://s.apache.org/CVE-2012-2138
- CVE-2013-2254 - Apache Sling denial of service vulnerability (October 9th, 2013), see http://s.apache.org/CVE-2013-2254
- CVE-2013-4390 - Apache Sling open redirect on login (October 20th, 2013), see http://s.apache.org/CVE-2013-4390