Security Bulletin - Database Security update fixes one vulnerability (CVE-2020-7339)
Security Bulletins ID:
SB10340
Last Modified: 2022-05-04 19:06:20 Etc/GMT
Last Modified: 2022-05-04 19:06:20 Etc/GMT
Summary
First Published: December 8, 2020
Article contents:
Database Security server contains a certificate used to communicate with the Database Activity Monitoring (DAM) sensor. This certificate has a SHA1 signature. This certificate cannot be updated by a system administrator and prior to version 4.8.0 required a software update to change the certificate. From version 4.8.0, we can update the certificate without the need to update the software.
CVE-2020-7339/CVE-2005-4900
Use of a Broken or Risky Cryptographic Algorithm vulnerability in Database Security Server and Sensor prior to 4.8.0 in the form of a SHA1 signed certificate that would allow an attacker on the same local network to potentially intercept communication between the Server and Sensors.
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-7339
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7339
Remediation
To remediate this issue, customers on Database Security server and sensor prior to version 4.8 should update to version 4.8.
Go to the Product Downloads site, and download the applicable product update files:
Download and Installation Instructions
For instructions to download product updates and hotfixes, see KB56057 - How to download Enterprise product updates and documentation. Review the Release Notes and the Installation Guide for instructions on how to install these updates. All documentation is available on the Product Documentation site.
Product Specific Notes
View the Database Security 4.8 product documentation.
Acknowledgments
We credit HCL Technologies Ltd. for responsibly reporting this flaw.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For Database Security server on Windows and Linux:
Use the following instructions for the Database Security server:
CVSS, or Common Vulnerability Scoring System, 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 judge 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 do not factor into a score any potential follow-on exploits that might be made possible by the successful exploitation of the issue being scored.
What are the CVSS scoring metrics?
CVE-2020-7339: Insecure use of a SHA1 signed certificate
NOTE: The below CVSS version 3.1 vector was used to generate this score.
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C&version=3.1
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: |
Database Security | All versions prior to 4.8.0 | CVE-2020-7339 | CWE-327: Use of a Broken or Risky Cryptographic Algorithm | Medium | 6.3 / 5.7 |
Recommendations: | Install or update to the latest versions listed in the Remediation section below | ||||
Security Bulletin Replacement: | None | ||||
Location of updated software: | Product Downloads site |
Article contents:
- Vulnerability Description
- Remediation
- Product Specific Notes
- Acknowledgments
- Frequently Asked Questions (FAQs)
- Resources
- Disclaimer
Database Security server contains a certificate used to communicate with the Database Activity Monitoring (DAM) sensor. This certificate has a SHA1 signature. This certificate cannot be updated by a system administrator and prior to version 4.8.0 required a software update to change the certificate. From version 4.8.0, we can update the certificate without the need to update the software.
CVE-2020-7339/CVE-2005-4900
Use of a Broken or Risky Cryptographic Algorithm vulnerability in Database Security Server and Sensor prior to 4.8.0 in the form of a SHA1 signed certificate that would allow an attacker on the same local network to potentially intercept communication between the Server and Sensors.
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-7339
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7339
Remediation
To remediate this issue, customers on Database Security server and sensor prior to version 4.8 should update to version 4.8.
Go to the Product Downloads site, and download the applicable product update files:
Product | Version | Type | File Name | Release Date |
Database Security server | 4.8 | Minor | McAfee-DBS-Server-installer-4.8.0-54444.exe mfe-dbs-server-jre-4.8.0-54444.i586.rpm.bin |
December 3, 2020 |
Database Security sensor | 4.8 | Minor | McAfee-DBS-Sensor-installer-x86-4.8.0-21393.exe McAfee-DBS-Sensor-installer-x86_64-4.8.0-21393.exe mfe-dbs-sensor-4.8.0-21393.i386.rpm.bin mfe-dbs-sensor-4.8.0-21393.x86_64.rpm.bin mfedbs.base.sensor.4.8.0-21393.bff.bin mfedbs.sensor-4.8.0-21393-HP-UX-ia64.depot.bin mfe-dbs-sensor_4.8.0-21393_i386.deb.bin mfe-dbs-sensor_4.8.0-21393_amd64.deb.bin MFEDBSsensor-4.8.0-21393-sparc64.pkg.bin MFEDBSsensor-4.8.0-21393-x86_64.pkg.bin |
December 3, 2020 |
Download and Installation Instructions
For instructions to download product updates and hotfixes, see KB56057 - How to download Enterprise product updates and documentation. Review the Release Notes and the Installation Guide for instructions on how to install these updates. All documentation is available on the Product Documentation site.
Product Specific Notes
View the Database Security 4.8 product documentation.
Acknowledgments
We credit HCL Technologies Ltd. for responsibly reporting this flaw.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For Database Security server on Windows and Linux:
Use the following instructions for the Database Security server:
- Install Wireshark on the server and enable capturing.
- Connect the Database Security sensor to the server.
- Analyze the Wireshark capture for the certificate used when communicating between the server and sensor.
CVSS, or Common Vulnerability Scoring System, 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 judge 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 do not factor into a score any potential follow-on exploits that might be made possible by the successful exploitation of the issue being scored.
What are the CVSS scoring metrics?
CVE-2020-7339: Insecure use of a SHA1 signed certificate
Base Score | 6.3 |
Attack Vector (AV) | Adjacent Network (A) |
Attack Complexity (AC) | Low (L) |
Privileges Required (PR) | None (N) |
User Interaction (UI) | None (N) |
Scope (S) | Unchanged (U) |
Confidentiality (C) | Low (L) |
Integrity (I) | Low (L) |
Availability (A) | Low (L) |
Temporal Score (Overall) | 5.7 |
Exploitability (E) | Proof-of-Concept (P) |
Remediation Level (RL) | Official Fix (O) |
Report Confidence (RC) | Confirmed (C) |
NOTE: The below CVSS version 3.1 vector was used to generate this score.
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C&version=3.1
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.