Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2024.0219
2024-01 Security Bulletin: Security Director Insights:
Multiple vulnerabilities in SDI
11 January 2024
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Security Director Insights
Publisher: Juniper Networks
Operating System: Juniper
Resolution: Patch/Upgrade
CVE Names: CVE-2023-26464 CVE-2022-23307 CVE-2022-23305
CVE-2022-23302 CVE-2021-44832 CVE-2021-44228
CVE-2020-9493 CVE-2019-17571 CVE-2016-2183
Original Bulletin:
https://supportportal.juniper.net/s/article/2024-01-Security-Bulletin-Security-Director-Insights-Multiple-vulnerabilities-in-SDI
Comment: CVSS (Max): 10.0 CVE-2021-44228 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H)
CVSS Source: Juniper
Calculator: https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- --------------------------BEGIN INCLUDED TEXT--------------------
Article ID: JSA75737
Product Affected: These issues affect all versions of Security Director
Insights .
Severity Level: Critical
CVSS Score: 10.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H)
Problem:
Security Director Insights release 23.1R1 addresses multiple vulnerabilities in
3rd party libraries found in prior releases with updated open source software
components.
These issues affect Juniper Networks Security Director Insights versions prior
to 23.1R1.
Juniper SIRT is not aware of any malicious exploitation of this vulnerability.
These issues were discovered during external security research.
The resolved issues include:
+--------------+----------+---------------------------------------------------+
| CVE | CVSS | Summary |
+--------------+----------+---------------------------------------------------+
| | |The DES and Triple DES ciphers, as used in the TLS,|
| |7.5 ( |SSH, and IPSec protocols and other protocols and |
| |CVSS:3.1/ |products, have a birthday bound of approximately |
|CVE-2016-2183 |AV:N/AC:L/|four billion blocks, which makes it easier for |
| |PR:N/UI:N/|remote attackers to obtain cleartext data via a |
| |S:U/C:H/ |birthday attack against a long-duration encrypted |
| |I:N/A:N ) |session, as demonstrated by an HTTPS session using |
| | |Triple DES in CBC mode, aka a "Sweet32" attack. |
+--------------+----------+---------------------------------------------------+
| |9.8 ( |Included in Log4j 1.2 is a SocketServer class that |
| |CVSS:3.1/ |is vulnerable to deserialization of untrusted data |
| |AV:N/AC:L/|which can be exploited to remotely execute |
|CVE-2019-17571|PR:N/UI:N/|arbitrary code when combined with a deserialization|
| |S:U/C:H/ |gadget when listening to untrusted network traffic |
| |I:H/A:H ) |for log data. This affects Log4j versions up to 1.2|
| | |up to 1.2.17. |
+--------------+----------+---------------------------------------------------+
| |9.8 ( | |
| |CVSS:3.1/ |A deserialization flaw was found in Apache Chainsaw|
|CVE-2020-9493 |AV:N/AC:L/|versions prior to 2.1.0 which could lead to |
| |PR:N/UI:N/|malicious code execution. |
| |S:U/C:H/ | |
| |I:H/A:H ) | |
+--------------+----------+---------------------------------------------------+
| | |JMSSink in all versions of Log4j 1.x is vulnerable |
| | |to deserialization of untrusted data when the |
| | |attacker has write access to the Log4j |
| | |configuration or if the configuration references an|
| |8.8 ( |LDAP service the attacker has access to. The |
| |CVSS:3.1/ |attacker can provide a |
| |AV:N/AC:L/|TopicConnectionFactoryBindingName configuration |
|CVE-2022-23302|PR:L/UI:N/|causing JMSSink to perform JNDI requests that |
| |S:U/C:H/ |result in remote code execution in a similar |
| |I:H/A:H ) |fashion to CVE-2021-4104. Note this issue only |
| | |affects Log4j 1.x when specifically configured to |
| | |use JMSSink, which is not the default. Apache Log4j|
| | |1.2 reached end of life in August 2015. Users |
| | |should upgrade to Log4j 2 as it addresses numerous |
| | |other issues from the previous versions. |
+--------------+----------+---------------------------------------------------+
| | |By design, the JDBCAppender in Log4j 1.2.x accepts |
| | |an SQL statement as a configuration parameter where|
| | |the values to be inserted are converters from |
| | |PatternLayout. The message converter, %m, is likely|
| | |to always be included. This allows attackers to |
| | |manipulate the SQL by entering crafted strings into|
| |9.8 ( |input fields or headers of an application that are |
| |CVSS:3.1/ |logged allowing unintended SQL queries to be |
|CVE-2022-23305|AV:N/AC:L/|executed. Note this issue only affects Log4j 1.x |
| |PR:N/UI:N/|when specifically configured to use the |
| |S:U/C:H/ |JDBCAppender, which is not the default. Beginning |
| |I:H/A:H ) |in version 2.0-beta8, the JDBCAppender was |
| | |re-introduced with proper support for parameterized|
| | |SQL queries and further customization over the |
| | |columns written to in logs. Apache Log4j 1.2 |
| | |reached end of life in August 2015. Users should |
| | |upgrade to Log4j 2 as it addresses numerous other |
| | |issues from the previous versions. |
+--------------+----------+---------------------------------------------------+
| |8.8 ( | |
| |CVSS:3.1/ |CVE-2020-9493 identified a deserialization issue |
|CVE-2022-23307|AV:N/AC:L/|that was present in Apache Chainsaw. Prior to |
| |PR:L/UI:N/|Chainsaw V2.0 Chainsaw was a component of Apache |
| |S:U/C:H/ |Log4j 1.2.x where the same issue exists. |
| |I:H/A:H ) | |
+--------------+----------+---------------------------------------------------+
| | |** UNSUPPORTED WHEN ASSIGNED ** When using the |
| | |Chainsaw or SocketAppender components with Log4j |
| | |1.x on JRE less than 1.7, an attacker that manages |
| |7.5 ( |to cause a logging entry involving a |
| |CVSS:3.1/ |specially-crafted (ie, deeply nested) hashmap or |
| |AV:N/AC:L/|hashtable (depending on which logging component is |
|CVE-2023-26464|PR:N/UI:N/|in use) to be processed could exhaust the available|
| |S:U/C:N/ |memory in the virtual machine and achieve Denial of|
| |I:N/A:H ) |Service when the object is deserialized. This issue|
| | |affects Apache Log4j before 2. Affected users are |
| | |recommended to update to Log4j 2.x. NOTE: This |
| | |vulnerability only affects products that are no |
| | |longer supported by the maintainer. |
+--------------+----------+---------------------------------------------------+
| | |Apache Log4j2 2.0-beta9 through 2.15.0 (excluding |
| | |security releases 2.12.2, 2.12.3, and 2.3.1) JNDI |
| | |features used in configuration, log messages, and |
| | |parameters do not protect against attacker |
| |10.0 ( |controlled LDAP and other JNDI related endpoints. |
| |CVSS:3.1/ |An attacker who can control log messages or log |
| |AV:N/AC:L/|message parameters can execute arbitrary code |
|CVE-2021-44228|PR:N/UI:N/|loaded from LDAP servers when message lookup |
| |S:C/C:H/ |substitution is enabled. From log4j 2.15.0, this |
| |I:H/A:H ) |behavior has been disabled by default. From version|
| | |2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this|
| | |functionality has been completely removed. Note |
| | |that this vulnerability is specific to log4j-core |
| | |and does not affect log4net, log4cxx, or other |
| | |Apache Logging Services projects. |
+--------------+----------+---------------------------------------------------+
| | |Apache Log4j2 versions 2.0-beta7 through 2.17.0 |
| |6.6 ( |(excluding security fix releases 2.3.2 and 2.12.4) |
| |CVSS:3.1/ |are vulnerable to a remote code execution (RCE) |
| |AV:N/AC:H/|attack when a configuration uses a JDBC Appender |
|CVE-2021-44832|PR:H/UI:N/|with a JNDI LDAP data source URI when an attacker |
| |S:U/C:H/ |has control of the target LDAP server. This issue |
| |I:H/A:H ) |is fixed by limiting JNDI data source names to the |
| | |java protocol in Log4j2 versions 2.17.1, 2.12.4, |
| | |and 2.3.2. |
+--------------+----------+---------------------------------------------------+
+++---------------------------------------------------------------------------+
||| Summary of weaknesses that were fixed for which no CVE IDs or CVSS scores |
||| have been assigned: |
+++---------------------------------------------------------------------------+
|||SSH Weak Message Authentication Code Algorithms: Running SSH service with |
|||insecure MAC algorithms in use: umac-64@openssh.com,umac-64-etm@openssh.com|
+++---------------------------------------------------------------------------+
|||TLS/SSL Weak Message Authentication Code Cipher Suites: |
|||TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, |
|||TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, |
|||TLS_RSA_WITH_CAMELLIA_128_CBC_SHA, TLS_RSA_WITH_CAMELLIA_256_CBC_SHA |
+++---------------------------------------------------------------------------+
|||SSH CBC vulnerability: A vulnerability exists in SSH messages that employ |
|||CBC mode that may allow an attacker to recover plaintext from a block of |
|||ciphertext. |
+++---------------------------------------------------------------------------+
|||TLS/SSL Server supports the Use of Static Key Ciphers: |
|||TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA256, |
|||TLS_RSA_WITH_AES_128_CCM, TLS_RSA_WITH_AES_128_CCM_8, |
|||TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA, |
|||TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_RSA_WITH_AES_256_CCM, |
|||TLS_RSA_WITH_AES_256_CCM_8, TLS_RSA_WITH_AES_256_GCM_SHA384, |
|||TLS_RSA_WITH_ARIA_128_GCM_SHA256, TLS_RSA_WITH_ARIA_256_GCM_SHA384, |
|||TLS_RSA_WITH_CAMELLIA_128_CBC_SHA, TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256, |
|||TLS_RSA_WITH_CAMELLIA_256_CBC_SHA, TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256 |
+++---------------------------------------------------------------------------+
Solution:
The following software releases have been updated to resolve this specific
issue: 23.1R1, and all subsequent releases.
This issue is being tracked as PR 1715013 which is visible on the Customer
Support website.
Note: Juniper SIRT's policy is not to evaluate releases which are beyond End of
Engineering (EOE) or End of Life (EOL).
Workaround:
Use access lists or firewalls to limit access to the device only from trusted
hosts.
Modification History:
2024-01-10: Initial Publication
Related Information:
o KB16613: Overview of the Juniper Networks SIRT Quarterly Security Bulletin
Publication Process
o KB16765: In which releases are vulnerabilities fixed?
o KB16446: Common Vulnerability Scoring System (CVSS) and Juniper's Security
Advisories
o Report a Security Vulnerability - How to Contact the Juniper Networks
Security Incident Response Team
Last Updated: 2024-01-10
Created: 2024-01-10
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
https://www.auscert.org.au/bulletins/
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: https://auscert.org.au/gpg-key/
iQIVAwUBZZ9RC8kNZI30y1K9AQjx1Q/+NRSp9Fdna3wtqvj9RSEmeHtiikG0ydQN
wnnc+FuQLHQgZBOMtMg22zZm2o/rZkw21cOqYrSFiIkw4vumbjwZNS6WvyHpqX28
Rhr6tloU2/R6ce088tRx74Dsp+IC0m9Vpb1ezOxc0wrFo6wrbqdJep35Dc5OXYXI
JgzH4GM7e+l5Ge/KKc0OVm/9zWwoKdXF8l+M4JwZS3XfMYfsE2FaDgR4Wc/mQz25
LpGTTPRCJOItnCPeduRWsWD/FJiR1Mvm77J/KoGCeSni79W4Up/ixTRHppk43pXp
qVYGbtrhelK3OBqNiQwZ3q51EF7NPDYwaz+W92FfKnmBM2cnXXPzWxiHTvpi+l4X
sU7oNvpGcH0pnCnZq4roBPT/jmnKwRkBSgp3WrIo6/TcfNi5IVOV9bCwpi5b/jEG
NGxDiRjvSKHWncOlYSqAPTKzeayMqqqN5PBzyDn27nakd0qFoNEgVmL+BMCZkCZY
BWIW73bNbdP9q60irhw0fY9LskpaRJKsoKEhWWcvuaVzLMED+4FI4RVG0HuAfp50
Zfr+3gMmt0N6Zci7PQDW1+YwuXBLa1s8bCXUrtCO1x/1rlw0jIrw2tqE07xCnK5I
Wz+Rvn53Bnc0BC4Qb9yhA82pyasK1XDylVikE4q0OoLdL8NCvKMm0jjNWtds2cWS
OQcU4oZOJrY=
=Ox7R
-----END PGP SIGNATURE-----