Security Bulletin - Threat Intelligence Exchange Server update fixes Linux kernel, OpenSSH, and OpenSSL vulnerabilities (CVE-2018-5391, CVE-2018-15473, CVE-2018-15919, CVE-2018-5407, and CVE-2018-0732)
Security Bulletins ID:
SB10269
Last Modified: 2022-05-04 15:35:36 Etc/GMT
Last Modified: 2022-05-04 15:35:36 Etc/GMT
Summary
First Published: February 12, 2019
Article contents:
This update remediates the following issues:
TIE Server Appliance:
To remediate this issue, go to the Product Downloads site, and download the applicable product update/hotfix file:
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.
Workaround
We strongly recommend that you install the available version update. If you cannot, consider the following workarounds:
These vulnerabilities were first disclosed by The MITRE Corporation as a CVE.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For Appliances:
Use the following instructions for Appliance-based products:
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 at: http://www.first.org/cvss/.
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?
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.
| Impact of Vulnerability: | Denial of Service (CWE-730, OWASP 2004:A9) Information Leak/Disclosure (CWE-717, OWASP 2004:A6) |
| CVE ID: | CVE-2018-5391 CVE-2018-15473 CVE-2018-15919 CVE-2018-0732 CVE-2018-5407 |
| Severity Rating: | CVE-2018-5391: High CVE-2018-15473: Medium CVE-2018-15919: Medium CVE-2018-0732: Medium CVE-2018-5407: Medium |
| CVSS v3 Base/Temporal Scores: | CVE-2018-5391: 7.5 / 6.6 CVE-2018-15473: 5.3 / 4.9 CVE-2018-15919: 5.3 / 4.9 CVE-2018-0732: 5.3 / 4.4 CVE-2018-5407: 4.7 / 4.2 |
| Recommendations: | Install or update to Threat Intelligence Exchange (TIE) Server:
|
| Security Bulletin Replacement: | None |
| Affected Software: | TIE Server 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.3.0 |
| Location of updated software: | Product Downloads site |
Article contents:
- Vulnerability Description
- Remediation
- Workaround
- Acknowledgments
- Frequently Asked Questions (FAQs)
- Resources
- Disclaimer
This update remediates the following issues:
- CVE-2018-5391:
The Linux kernel, versions 3.9+, is vulnerable to a denial of service attack with low rates of specially modified packets targeting IP fragment re-assembly. An attacker may cause a denial of service condition by sending specially crafted IP fragments.
https://nvd.nist.gov/vuln/detail/CVE-2018-5391
- CVE-2018-15473:
OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.
https://nvd.nist.gov/vuln/detail/CVE-2018-15473
- CVE-2018-15919:
Remotely observable behavior in auth-gss2.c in OpenSSH through 7.8 could be used by remote attackers to detect existence of users on a target system when GSS2 is in use.
https://nvd.nist.gov/vuln/detail/CVE-2018-15919
- CVE-2018-0732:
During key agreement in a TLS handshake using a DH(E) based ciphersuite, a malicious server can send a very large prime value to the client. This will cause the client to spend an unreasonably long period of time generating a key for this prime resulting in a hang until the client has finished. This could be exploited in a Denial Of Service attack.
https://nvd.nist.gov/vuln/detail/CVE-2018-0732
- CVE-2018-5407:
OpenSSL ECC scalar multiplication, used in, for example, ECDSA and ECDH, has been shown to be vulnerable to a microarchitecture timing side channel attack. An attacker with sufficient access to mount local timing attacks during ECDSA signature generation could recover the private key.
https://www.openssl.org/news/vulnerabilities.html#2018-0734
https://nvd.nist.gov/vuln/detail/CVE-2018-5407
TIE Server Appliance:
- Linux Kernel
- OpenSSH
- OpenSSL
To remediate this issue, go to the Product Downloads site, and download the applicable product update/hotfix file:
| Product | Version | Type | File Name | Release Date |
| TIE Server | 2.3.1 | Version Update | TIE Server 2.3.1.116.1 | February 12, 2019 |
| TIE Server | 2.2.0 | Hotfix | TIE Server 2.2.0 HF1 | April 23, 2019 |
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.
Workaround
We strongly recommend that you install the available version update. If you cannot, consider the following workarounds:
- CVE-2018-539:
Reduce the limits on memory usage for incomplete fragmented packets by following these steps as root user in the TIE Servers:
- Edit /etc/sysctl.conf and set the following values:
net.ipv4.ipfrag_low_thresh = 196608
net.ipv4.ipfrag_high_thresh = 262144
net.ipv6.ip6frag_low_thresh = 196608
net.ipv6.ip6frag_high_thresh = 262144
- Run the following commands:
sysctl -w net.ipv4.ipfrag_low_thresh=196608
sysctl -w net.ipv4.ipfrag_high_thresh=262144
sysctl -w net.ipv6.ip6frag_low_thresh=196608
sysctl -w net.ipv6.ip6frag_high_thresh=262144
- Edit /etc/sysctl.conf and set the following values:
- CVE-2018-15473:
Update OpenSSH to 7.4p1-17 or later. For more information, see KB90843.
- CVE-2018-15919:
Disable GSS authentication in OpenSSH by following these steps as root user in the TIE Servers:
- Edit /etc/ssh/sshd_config and set the following value:
GSSAPIAuthentication no
- Restart OpenSSH with the following command:
service sshd restart
- Edit /etc/ssh/sshd_config and set the following value:
- CVE-2018-0732:
Update OpenSSL to 1.0.2q or later. For more information, see KB90843.
- CVE-2018-5407:
Update OpenSSL to 1.0.2q or later. For more information, see KB90843.
These vulnerabilities were first disclosed by The MITRE Corporation as a CVE.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For Appliances:
Use the following instructions for Appliance-based products:
- Open the Administrator's User Interface (UI).
- Click the About link. The product version displays.
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 at: http://www.first.org/cvss/.
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-2018-5391: kernel: IP fragments with random offsets allow a remote denial of service (FragmentSmack)
Base Score 7.5 Attack Vector (AV) Network (N) 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) None (N) Availability (A) High (H) Temporal Score (Overall) 6.6 Exploitability (E) Unproven (U) Remediation Level (RL) Temporary Fix (T) Report Confidence (RC) Confirmed (C)
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:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:T/RC:C
- CVE-2018-15473: OpenSSH: User enumeration via malformed packets in authentication requests
Base Score 5.3 Attack Vector (AV) Network (N) 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) None (N) Availability (A) None (N) Temporal Score (Overall) 4.9 Exploitability (E) Functional (F) 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://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C
- CVE-2018-15919: OpenSSH: User enumeration via malformed packets in authentication requests
Base Score 5.3 Attack Vector (AV) Network (N) 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) None (N) Availability (A) None (N) Temporal Score (Overall) 4.9 Exploitability (E) Functional (F) 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://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C
- CVE-2018-0732: OpenSSL: Malicious server can send large prime to client during DH(E) TLS handshake causing the client to hang
Base Score 5.3 Attack Vector (AV) Network (N) 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 (H) Temporal Score (Overall) 4.4 Exploitability (E) Unproven (U) Remediation Level (RL) Official Fix (O) Report Confidence (RC) Reasonable (R)
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:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:R
- CVE-2018-5407: OpenSSL: Side-channel vulnerability on SMT/Hyper-Threading architectures (PortSmash)
Base Score 4.7 Attack Vector (AV) Local (L) Attack Complexity (AC) High (H) Privileges Required (PR) Low (L) User Interaction (UI) None (N) Scope (S) Unchanged (U) Confidentiality (C) High (H) Integrity (I) None (N) Availability (A) None (N) Temporal Score (Overall) 4.2 Exploitability (E) Functional (F) 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://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N/E:P/RL:O/RC:C
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.
