Loading...

Knowledge Center


McAfee Security Bulletin: Threat Intelligence Exchange 1.3.0 addresses multiple issues related to its database server and OpenSSL
Security Bulletins ID:   SB10152
Last Modified:  4/7/2017

Summary

First Published: 3/29/2016
 
 Impact of Vulnerability:  Authentication Bypass by Spoofing (CWE-290)
 Use of a Broken or Risky Cryptographic Algorithm (CWE-327)
 Uncontrolled Resource Consumption (CWE-400)
 Out-of-bounds Write (CWE-787)
 CVE Numbers:  CVE-2016-0773
 CVE-2016-2842
 Severity Rating:  Medium
 Base / Overall CVSS v3 Scores:
  • Database authentication is vulnerable to IP spoofing attacks: 5.5
  • CVE-2016-2842: 5.4
  • Use of the MD5 algorithm by PostgreSQL for sensitive data at rest: 4.2
  • CVE-2016-0773: 4.8
 Recommendations:  Upgrade to Threat Intelligence Exchange (TIE) Server 1.3.0
 Security Bulletin Replacement:  None
 Affected Software:  TIE Server 1.2.1 and earlier
 Location of Updated Software:  http://www.mcafee.com/us/downloads/downloads.aspx

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:

Description

This update resolves the following issues:
  • Database authentication is vulnerable to IP spoofing attacks
    In addition to password authentication, the PostgreSQL database in TIE Server is configured to deny all connection attempts except for those whose source IP address belongs to a trusted host. This IP address-based authentication could be subject to IP spoofing attacks in which an attacker impersonates one of those trusted hosts.
     
  • OpenSSL – Internal function does not verify successful memory allocation potentially resulting in a denial of service (CVE-2016-2842)
    The doapr_outch function in crypto/bio/b_print.c in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g does not verify that a certain memory allocation succeeds. This allows remote attackers to cause a denial of service (out-of-bounds write or memory consumption) or possibly have unspecified other impact using a long string, as demonstrated by a large amount of ASN.1 data. This is a different vulnerability from CVE-2016-0799.
    https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-2842
     
  • Use of the MD5 algorithm by PostgreSQL for sensitive data at rest
    The TIE Server uses a PostgreSQL database internally. In TIE Server 1.2.1 and earlier, user authentication is through passwords. Passwords are hashed and salted using MD5, a cryptographically weaker hashing algorithm. Possession of the salted hash allows authentication to the TIE Server. In TIE Server 1.2.1, hashes are protected in transit from passive sniffing using TLS. However, the salted, hashed passwords are stored in the PostgreSQL database. Note that access to these hashed passwords is limited to the system user running the PostgreSQL service, the root user, and database super-users.
     
  • PostgreSQL - Regular expressions are vulnerable to a denial of service (CVE-2016-0773)
    PostgreSQL 9.3.x before 9.3.11 allows remote attackers to cause a denial of service (infinite loop or buffer overflow and crash) using a large Unicode character range in a regular expression. TIE Server 1.2.1 and earlier ships with PostgreSQL 9.3.10 and uses regular expressions, and is therefore vulnerable.
    https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0773

Remediation

The database issues are resolved in Threat Intelligence Exchange Server 1.3.0 by updating PostgreSQL to 9.3.11 and replacing the password-based authentication with certificate-based authentication.

The OpenSSL vulnerability is resolved by updating the library version to 1.0.1s.

Go to the Product Downloads site and download the applicable product patch file:
 
Product Type Version File Name Release Date
TIE Server 1.3.0 Update 1.3.0 TIEServer_1.3.0.235.x86_64-MAIN March 29, 2016

Additional Patch Information
For additional information on these updates, such as remediation steps and compatibility issues, see PD26435 - Threat Intelligence Exchange 1.3.0 Release Notes.
 
Download and Installation Instructions
See KB56057 for instructions on how to download McAfee products, documentation, security updates, patches, and hotfixes. Review the Release Notes and the Installation Guide, which you can download from the Documentation tab, for instructions on how to install these updates.

Workaround

None. Install the provided patch update.

Mitigations

Mitigations are provided along with the security fixes packaged in the release.

Acknowledgements

None.

Frequently Asked Questions (FAQs)

How do I know whether my McAfee product is vulnerable or not?

For Endpoint products:
Use the following instructions for endpoint or client based products:
  1. Right-click on the McAfee tray shield icon on the Windows task bar.
  2. Select Open Console.
  3. In the console, select Action Menu.
  4. In the Action Menu, select Product Details. The product version is displayed.
For ePO:
Check the version and build of ePO that is installed. For information on how to check the version, see KB52634.

For Appliances:
Use the following instructions for Appliance based products:
  1. Open the Administrator's User Interface (UI).
  2. Click the About link. The product version is displayed.
What is CVSS?
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, please visit the CVSS website at: http://www.first.org/cvss/.

When calculating CVSS v2 scores, McAfee has 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 successful exploitation of the issue being scored.

CVSS v3 scoring is in final review as of December 2015. CVSS v2 will be replaced with CVSS v3 when v3 is fully approved. Security bulletins will have scores for both versions for at least 6 months after v3 is fully approved.
https://www.first.org/cvss/v3/development
https://www.first.org/cvss/calculator/3.0
 
What are the CVSS scoring metrics that have been used?
 
Database authentication is vulnerable to IP spoofing attacks:
 
CVSS v3.0 Scoring:
 
 Base Score 5.5
 Attack Vector (AV) Adjacent (A)
 Attack Complexity (AC) Low (L)
 Privileges Required (PR) Low (L)
 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.1
 Exploitability (E) Functional (F)
 Remediation Level (RL) Official Fix (O)
 Report Confidence (RC) Not Defined (X)

NOTE: The below CVSS version 3.0 vector was used to generate this score.
https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:F/RL:O
 
OpenSSL - Internal function does not verify successful memory allocation potentially resulting in a denial of service (CVE-2016-2842):
 
CVSS v3.0 Scoring:
 
 Base Score 5.4
 Attack Vector (AV) Adjacent (A)
 Attack Complexity (AC) Low (L)
 Privileges Required (PR) None (N)
 User Interaction (UI) None (N)
 Scope (S) Unchanged (U)
Confidentiality (C) None (N)
Integrity (I) Low (L)
Availability (A) Low (L)
 Temporal Score (Overall) 4.3
 Exploitability (E) Unproven (U)
 Remediation Level (RL) Official Fix (O)
 Report Confidence (RC) Unknown (U)

NOTE: The below CVSS version 3.0 vector was used to generate this score.
https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L/E:U/RL:O/RC:U
 
Use of the MD5 algorithm by PostgreSQL for sensitive data at rest:
 
CVSS v3.0 Scoring:
 
 Base Score 4.2
 Attack Vector (AV) Local (L)
 Attack Complexity (AC) Low (L)
 Privileges Required (PR) High (H)
 User Interaction (UI) None (N)
 Scope (S) Unchanged (U)
Confidentiality (C) Low (L)
Integrity (I) Low (L)
Availability (A) Low (L)
 Temporal Score (Overall) 3.9
 Exploitability (E) Functional (F)
 Remediation Level (RL) Official Fix (O)
 Report Confidence (RC) Not Defined (X)

NOTE: The below CVSS version 3.0 vector was used to generate this score.
https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L/E:F/RL:O
 
PostgreSQL - Regular expressions are vulnerable to a denial of service (CVE-2016-0773):
 
CVSS v3.0 Scoring:
 
 Base Score 4.8
 Attack Vector (AV) Adjacent Network (A)
 Attack Complexity (AC) High (H)
 Privileges Required (PR) Low (L)
 User Interaction (UI) None (N)
 Scope (S) Unchanged (U)
Confidentiality (C) None (N)
Integrity (I) None (N)
Availability (A) High (L)
 Temporal Score (Overall) 4.2
 Exploitability (E) Unproven that exploit exists (U)
 Remediation Level (RL) Official Fix (O)
 Report Confidence (RC) Confirmed (C)

NOTE: The below CVSS version 3.0 vector was used to generate this score.
https://nvd.nist.gov/cvss/v3-calculator?vector=AV:A/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C

Where can I find a list of all security bulletins or how do I report a product vulnerability?
To find a list of all security bulletins, or if you have information about a security issue or vulnerability with a McAfee product, please visit our product security website at: http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx.

Resources

To contact Technical Support, log on to the ServicePortal and go to the Create a Service Request page at https://support.mcafee.com/ServicePortal/faces/serviceRequests/createSR:
  • 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 required fields. Your password and logon instructions will be emailed to you.

Disclaimer

The information provided in this security bulletin is provided as is without warranty of any kind. McAfee disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall McAfee or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits, or special damages, even if McAfee or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
 
Any future product release dates mentioned in this security bulletin are intended to outline our general product direction and they should not 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 are not 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 remains at our sole discretion and may be changed or cancelled at any time.

Rate this document

Beta Translate with

Select a desired language below to translate this page.

Languages:

This article is available in the following languages:

English United States
Japanese

Glossary of Technical Terms


 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.