<Past |
Future> |
1.2.14 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.2.15 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.2.16 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.2.17 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.21.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.0 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.1 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.2 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.3 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.4 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.7 |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.9.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.10.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.11.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.12.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.13.x |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.14.x |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.15.x |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.16.x |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.17.x |
Approved w/Constraints [4, 5, 7, 8] |
Approved w/Constraints [4, 5, 7, 8] |
Approved w/Constraints [4, 5, 8, 9] |
Divest [4, 5, 8, 9] |
Divest [3, 8, 9, 10, 11, 12, 13] |
Divest [3, 8, 9, 10, 11, 12, 13] |
Divest [3, 8, 9, 10, 11, 12, 13] |
Divest [3, 8, 11, 12, 13, 14, 15] |
Divest [3, 8, 11, 12, 13, 14, 15] |
Unapproved |
Unapproved |
Unapproved |
2.18.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.19.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [4, 5, 8, 9] |
Divest [3, 8, 9, 10, 11, 12, 13] |
Divest [3, 8, 9, 10, 11, 12, 13] |
Divest [3, 8, 9, 10, 11, 12, 13] |
Divest [3, 8, 11, 12, 13, 14, 15] |
Divest [3, 8, 11, 12, 13, 14, 15] |
Divest [8, 11, 12, 13, 14, 15] |
Unapproved |
Unapproved |
2.20.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 8, 9, 10, 11, 12, 13] |
Approved w/Constraints [3, 8, 9, 10, 11, 12, 13] |
Approved w/Constraints [3, 8, 9, 10, 11, 12, 13] |
Divest [3, 8, 11, 12, 13, 14, 15] |
Divest [3, 8, 11, 12, 13, 14, 15] |
Divest [8, 11, 12, 13, 14, 15] |
Divest [8, 11, 12, 13, 14, 15] |
Divest [8, 11, 12, 13, 14, 15] |
2.21.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 8, 11, 12, 13, 14, 15] |
Approved w/Constraints [3, 8, 11, 12, 13, 14, 15] |
Divest [8, 11, 12, 13, 14, 15] |
Divest [8, 11, 12, 13, 14, 15] |
Divest [8, 11, 12, 13, 14, 15] |
2.22.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [8, 11, 12, 13, 14, 15] |
Divest [8, 11, 12, 13, 14, 15] |
Divest [8, 11, 12, 13, 14, 15] |
2.23.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [8, 11, 12, 13, 14, 15] |
Approved w/Constraints [8, 11, 12, 13, 14, 15] |
Approved w/Constraints [8, 11, 12, 13, 14, 15] |
| | [1] | This technology may not be used with Apache versions before 3.0.6 due to Common Vulnerabilities and Exposures (CVE)-2012-5616. | | [2] | As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
| | [3] | Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities. | | [4] | Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations. | | [5] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities. | | [6] | This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- Developers need to stay informed about the Apache Log4J development activities to ensure updates and patches to the software are tested and installed in a timely manner. Additionally, developers need to constantly monitor the various resources within the Apache community to get the most up-to-date information on known vulnerabilities as well as solutions to mitigate or remediate the vulnerabilities.
- All versions of Apache Log4j prior to 2.8.2 must be upgraded to 2.11.1 as soon as possible and version 2.11.1 should be the only approved version due to the vulnerability identified in CVE-2017-5645.
- When using Apache Log4J to process, store, and transmit VA sensitive information, it should be installed on specifically FIPS-compliant servers configured to use FIPS-compliant algorithms for encryption. If it is not technically possible to employ FIPS 140-2 encryption, then Apache Log4J should not be used with VA sensitive data.
| | [7] | This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- Developers need to stay informed about the Apache Log4J development activities to ensure updates and patches to the software are tested and installed in a timely manner. Additionally, developers need to constantly monitor the various resources within the Apache community to get the most up-to-date information on known vulnerabilities as well as solutions to mitigate or remediate the vulnerabilities.
- Administrators must ensure that they check vulnerability reporting sites and remediate any published vulnerabilities for Apache Log4J as soon as possible.
- Apache Log4J will require a 3rd party FIPS 140-2 certified solution for any
data containing PHI/PII or VA sensitive information.
| | [8] | This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product. | | [9] | This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Users must not utilize, Apache Log4j2 2.0-beta9 through 2.12.1 and 2.13.0 through 2.15.0 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints.
Per the Initial Product Review, users must abide by the following constraints:
- Developers need to stay informed about the Apache Log4J development activities to ensure updates and patches to the software are tested and installed in a timely manner. Additionally, developers need to constantly monitor the various resources within the Apache community to get the most up-to-date information on known vulnerabilities as well as solutions to mitigate or remediate the vulnerabilities.
- Administrators must ensure that they check vulnerability reporting sites and remediate any published vulnerabilities for Apache Log4J as soon as possible.
- Apache Log4J will require a 3rd party FIPS 140-2 certified solution for any
data containing PHI/PII or VA sensitive information.
In accordance with Emergency Directive (ED) 22-02 Mitigate Apache Log4j Vulnerability: When updates are available, agencies must update software using Log4j to the newest version and must not utilize previous versions, which is the most effective and manageable long-term option. Where updating is not possible, the following mitigating measures can be considered as a temporary solution and apply to the entire solution stack.
- Disable Log4j library. Disabling software using the Log4j library is an effective measure, favoring controlled downtime over adversary-caused issues. This option could cause operational impacts and limit visibility into other issues.
- Disable JNDI lookups or disable remote codebases. This option, while effective, may involve developer work and could impact functionality.
- Disconnect affected stacks. Solution stacks not connected to agency networks pose a dramatically lower risk from attack. Consider temporarily disconnecting the stack from agency networks.
- Isolate the system. Create a “vulnerable network” VLAN and segment the solution stack from the rest of the enterprise network.
- Deploy a properly configured Web Application Firewall (WAF) in front of the solution stack. Deploying a WAF is an important, but incomplete, solution. While threat actors will be able to bypass this mitigation, the reduction in alerting will allow an agency SOC to focus on a smaller set of alerts.
- Apply micropatch. There are several micropatches available. They are not a part of the official update but may limit agency risk.
| | [10] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | [11] | Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations. | | [12] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | [13] | The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website. | | [14] | This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
This technology must use the latest version of Java Development Kit (JDK) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- Developers need to stay informed about the Apache Log4J development activities to ensure updates and patches to the software are tested and installed in a timely manner. Additionally, developers need to constantly monitor the various resources within the Apache community to get the most up-to-date information on known vulnerabilities as well as solutions to mitigate or remediate the vulnerabilities.
- Administrators must ensure that they check vulnerability reporting sites and remediate any published vulnerabilities for Apache Log4J as soon as possible.
- Apache Log4J will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
Users must not utilize, Apache Log4j2 2.0-beta9 through 2.12.1 and 2.13.0 through 2.15.0 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints.
In accordance with Emergency Directive (ED) 22-02 Mitigate Apache Log4j Vulnerability: When updates are available, agencies must update software using Log4j to the newest version and must not utilize previous versions, which is the most effective and manageable long-term option. Where updating is not possible, the following mitigating measures can be considered as a temporary solution and apply to the entire solution stack.
- Disable Log4j library. Disabling software using the Log4j library is an effective measure, favoring controlled downtime over adversary-caused issues. This option could cause operational impacts and limit visibility into other issues.
- Disable JNDI lookups or disable remote codebases. This option, while effective, may involve developer work and could impact functionality.
- Disconnect affected stacks. Solution stacks not connected to agency networks pose a dramatically lower risk from attack. Consider temporarily disconnecting the stack from agency networks.
- Isolate the system. Create a “vulnerable network” VLAN and segment the solution stack from the rest of the enterprise network.
- Deploy a properly configured Web Application Firewall (WAF) in front of the solution stack. Deploying a WAF is an important, but incomplete, solution. While threat actors will be able to bypass this mitigation, the reduction in alerting will allow an agency SOC to focus on a smaller set of alerts.
- Apply micropatch. There are several micropatches available. They are not a part of the official update but may limit agency risk.
| | [15] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. |
|
Note: |
At the time of writing, version 2.23.1 is the most current version, released 03/06/2024. |