Title: Reporting Security Problems with Apache Notice: Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Security Updates # {#discovering} Lists of security problems fixed in released versions of the Apache HTTP Server are available: - [Apache 2.4 Security Vulnerabilities](/security/vulnerabilities_24.html) To get notification of when new security issues are fixed, join the [Apache HTTP Server Announcements list](http://httpd.apache.org/lists.html#http-announce) # Reporting New Security Problems with the Apache HTTP Server # {#reporting} The Apache Software Foundation takes a very active stance in eliminating security problems and denial of service attacks against the Apache HTTP server. We strongly encourage folks to report such problems to the private security mailing list of the ASF Security Team, before disclosing them in a public forum. Please see the page of the [ASF Security Team](http://www.apache.org/security/) for further information and contact information. **The Security Team cannot accept regular bug reports or other queries, we ask that you use our [bug reporting page](/bug_report.html) for those.** **All mail sent to the Security Team that does not relate to security problems in Apache software will be ignored.** 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. [More security tips](http://httpd.apache.org/docs/trunk/misc/security_tips.html) # Security Standards # {#standards} Apache HTTP Server vulnerabilities are labelled with [CVE](http://cve.mitre.org) (Common Vulnerabilities and Exposures) identifiers. # Historical Releases # {#historical} Earlier versions of Apache HTTP Server are no longer receiving security updates and should not be used. - [Apache 2.2 Historical Security Vulnerabilities (2005-2017)](/security/vulnerabilities_22.html) - [Apache 2.0 Historical Security Vulnerabilities (2002-2013)](/security/vulnerabilities_20.html) - [Apache 1.3 Historical Security Vulnerabilities (1998-2010)](/security/vulnerabilities_13.html)