Security Bulletin - Data Exchange Layer Broker update addresses multiple third-party library vulnerabilities (Java, OpenSSL, Log4J, and RSA BSAFE Crypto-J)
Security Bulletins ID:
SB10389
Last Modified: 2022-10-04 12:53:40 Etc/GMT
Last Modified: 2022-10-04 12:53:40 Etc/GMT
Summary
First Published: October 4, 2022
Article contents: Vulnerability Description
This DXL Broker release updates the following third-party libraries to resolve security issues. This Security Bulletin has been released to provide details for the listed third-party libraries as we have received a number of queries from customers asking about our status. Third-party libraries are updated regularly and only called out in Security Bulletins if we receive a significant number of queries.
To remediate this issue:
Download and Installation Instructions
For instructions to download product updates and hotfixes, see KB56057 - How to download product updates and documentation. Review the Release Notes and the Installation Guide for instructions on how to install these updates. All documentation is available at our Product Documentation site.
Frequently Asked Questions (FAQs)
How do I know if my DXL Broker is vulnerable or not?
Use the following instructions to check the DXL Broker version:
Common Vulnerability Scoring System (CVSS) is the result of the National Infrastructure Advisory Council's effort to standardize a system of assessing the criticality of a vulnerability. This system offers an unbiased criticality score between 0 and 10 that customers can use to determine how critical a vulnerability is and plan accordingly. For more information, visit the CVSS website.
When calculating CVSS scores, we've adopted a philosophy that fosters consistency and repeatability. Our guiding principle for CVSS scoring is to score the exploit under consideration by itself. We consider only the immediate and direct impact of the exploit under consideration. We don't factor into a score any potential follow-on exploits that might be made possible by the successful exploitation of the issue being scored.
Where can I find a list of all Security Bulletins?
All Security Bulletins are published on our Knowledge Center. Security Bulletins are retired (removed) once a product is both End of Sale and End of Support (End of Life).
How do I report a product vulnerability to you?
If you have information about a security issue or vulnerability with a product, follow the instructions provided in KB95563 - Report a vulnerability.
How do you respond to this and any other reported security flaws?
Our key priority is the security of our customers. If a vulnerability is found within any of our software or services, we work closely with the relevant security software development team to ensure the rapid and effective development of a fix and communication plan.
We only publish Security Bulletins if they include something actionable such as a workaround, mitigation, version update, or hotfix. Otherwise, we would simply be informing the hacker community that our products are a target, putting our customers at greater risk. For products that are updated automatically, a non-actionable Security Bulletin might be published to acknowledge the discoverer.
To view our PSIRT policy, see KB95564 - About PSIRT.
Resources
Disclaimer
The information provided in this Security Bulletin is provided as is without warranty of any kind. We disclaim all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall we or our suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits, or special damages, even if we or our suppliers have been advised of the possibility of such damages. Some states don't allow the exclusion or limitation of liability for consequential or incidental damages, so the preceding limitation may not apply.
Any future product release dates mentioned in this Security Bulletin are intended to outline our general product direction, and they shouldn't be relied on in making a purchasing decision. The product release dates are for information purposes only, and may not be incorporated into any contract. The product release dates aren't a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remain at our sole discretion and may be changed or canceled at any time.
| Product | Impacted Versions | CVE ID | Impact of Vulnerabilities | Severity Ratings | CVSS v3.1 Base/Temporal Scores |
| Data Exchange Layer (DXL) Broker | 6.0.0 5.x |
Java multiple CVEs | See Java CVEs Security Advisory link below. | ||
| OpenSSL multiple CVEs | See OpenSSL CVEs Security Advisory link below. | ||||
| Log4J multiple CVEs | See Log4J CVEs Security Advisory link below. | ||||
| RSA BSAFE Crypto-J CVE-2019-3738 | CWE-347: Improper Verification of Cryptographic Signature | Medium | 6.5 | ||
| Recommendations | Install or update to DXL Broker hotfix 6.0.0.301 | ||||
| Security Bulletin Replacement | None | ||||
| Location of updated software | Product Downloads site | ||||
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
Article contents: Vulnerability Description
This DXL Broker release updates the following third-party libraries to resolve security issues. This Security Bulletin has been released to provide details for the listed third-party libraries as we have received a number of queries from customers asking about our status. Third-party libraries are updated regularly and only called out in Security Bulletins if we receive a significant number of queries.
- Java has been updated to the latest July 2022 Java update (1.8.0_341)
Reference: Java Security Advisory
- OpenSSL has been updated to the latest build 1.0.2zf
Reference: OpenSSL Security Advisory
- Log4J has been updated to the latest build 2.18.0
Reference: Log4J Security Advisory
- RSA BSAFE Crypto-J library has been updated to the latest build 6.2.5
CVE-2019-3738
To remediate this issue:
- Customers using DXL Broker 5.x should update to hotfix 6.0.0.301 along with upgrading the ePO DXL extension to 6.0.0.301 included in this hotfix.
- Customers using DXL Broker 6.0.0.x should update to hotfix 6.0.0.301 along with upgrading the ePO DXL extension to 6.0.0.301 included in this hotfix.
| Product | Version | Type | Release Date |
| DXL Broker | 6.0.0.301 | Hotfix | October 4, 2022 |
Download and Installation Instructions
For instructions to download product updates and hotfixes, see KB56057 - How to download product updates and documentation. Review the Release Notes and the Installation Guide for instructions on how to install these updates. All documentation is available at our Product Documentation site.
Frequently Asked Questions (FAQs)
How do I know if my DXL Broker is vulnerable or not?
Use the following instructions to check the DXL Broker version:
- From the ePO System Tree, select your Windows DXL Broker system.
- Click the Products tab to verify the DXL Broker and version.
Common Vulnerability Scoring System (CVSS) is the result of the National Infrastructure Advisory Council's effort to standardize a system of assessing the criticality of a vulnerability. This system offers an unbiased criticality score between 0 and 10 that customers can use to determine how critical a vulnerability is and plan accordingly. For more information, visit the CVSS website.
When calculating CVSS scores, we've adopted a philosophy that fosters consistency and repeatability. Our guiding principle for CVSS scoring is to score the exploit under consideration by itself. We consider only the immediate and direct impact of the exploit under consideration. We don't factor into a score any potential follow-on exploits that might be made possible by the successful exploitation of the issue being scored.
Where can I find a list of all Security Bulletins?
All Security Bulletins are published on our Knowledge Center. Security Bulletins are retired (removed) once a product is both End of Sale and End of Support (End of Life).
How do I report a product vulnerability to you?
If you have information about a security issue or vulnerability with a product, follow the instructions provided in KB95563 - Report a vulnerability.
How do you respond to this and any other reported security flaws?
Our key priority is the security of our customers. If a vulnerability is found within any of our software or services, we work closely with the relevant security software development team to ensure the rapid and effective development of a fix and communication plan.
We only publish Security Bulletins if they include something actionable such as a workaround, mitigation, version update, or hotfix. Otherwise, we would simply be informing the hacker community that our products are a target, putting our customers at greater risk. For products that are updated automatically, a non-actionable Security Bulletin might be published to acknowledge the discoverer.
To view our PSIRT policy, see KB95564 - About PSIRT.
Resources
To contact Technical Support, go to the Create a Service Request page and log on to the ServicePortal.
- If you are a registered user, type your User ID and Password, and then click Log In.
- If you are not a registered user, click Register and complete the fields to have your password and instructions emailed to you.
Disclaimer
The information provided in this Security Bulletin is provided as is without warranty of any kind. We disclaim all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall we or our suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits, or special damages, even if we or our suppliers have been advised of the possibility of such damages. Some states don't allow the exclusion or limitation of liability for consequential or incidental damages, so the preceding limitation may not apply.
Any future product release dates mentioned in this Security Bulletin are intended to outline our general product direction, and they shouldn't be relied on in making a purchasing decision. The product release dates are for information purposes only, and may not be incorporated into any contract. The product release dates aren't a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remain at our sole discretion and may be changed or canceled at any time.
