jvz commented on code in PR #1948: URL: https://github.com/apache/logging-log4j2/pull/1948#discussion_r1385483165
########## src/site/asciidoc/security.adoc: ########## @@ -0,0 +1,313 @@ +//// + 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 + + https://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. +//// + +:cve-url-prefix: https://nvd.nist.gov/vuln/detail + += Security + +The Apache Log4j Security Team takes security seriously. +This allows our users to place their trust in Log4j for protecting their mission-critical data. +In this page we will help you find guidance on security-related issues and access to known vulnerabilities. + +include::_log4j1-eol.adoc[] + +[#support] +== Getting support + +If you need help on building or configuring Log4j or other help on following the instructions to mitigate the known vulnerabilities listed here, please use our xref:support.adoc#discussions[user support channels]. + +[TIP] +==== +If you need to apply a source code patch, use the building instructions for the Log4j version that you are using. +These instructions can be found in `BUILDING.md` distributed with the sources. +==== + +[#reporting] +== Reporting vulnerabilities + +If you have encountered an unlisted security vulnerability or other unexpected behaviour that has a security impact, or if the descriptions here are incomplete, please report them **privately** to mailto:[email protected][the Log4j Security Team]. + +[WARNING] +==== +Reports assuming attacker's access to the Log4j configuration will not qualify as a vulnerability. Review Comment: We can probably expand on this a little bit. Kind of like: "The threat model that Log4j uses considers configuration files as safe input controlled by the programmer; potential vulnerabilities that require the ability to modify a configuration are not considered vulnerabilities as the required access to do so implies the attacker can execute arbitrary code." Or something along those lines. Essentially, our general threat model revolves around log messages or other user input that can cause itself to be processed in such a way that it breaks security expectations. For example, logging a string that looks like a template string shouldn't expand the template since that's not an intentional feature. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
