Security Bulletin - Web Gateway update fixes several third-party vulnerabilities (CVE-2018-16864, CVE-2018-16865, CVE-2018-10897, CVE-2018-6485, CVE-2016-4463, CVE-2018-0494, and CVE-2018-18311)
Security Bulletins ID:
SB10276
Last Modified: 2022-05-04 15:40:29 Etc/GMT
Last Modified: 2022-05-04 15:40:29 Etc/GMT
Summary
First Published: March 12, 2019
MWG 7.7.2.20 includes the fix for CVE-2018-15473 that was addressed previously in 7.8 and 8.0, and is described in SB10267. CVE-2018-16395 from the same Security Bulletin does not apply to 7.7.2.x.
MWG 7.7.2.20 does not include the fix for CVE-2018-18311 and CVE-2018-6485.
Article contents:
These vulnerabilities were reported against the Open Source operating system that MWG runs on:
To remediate this issue, go to the Product Downloads site, and download the applicable product update file:
Download and Installation Instructions
All documentation and software relating to this and other MWG releases can be found on the Content & Cloud Security Portal.
Workaround
None.
Acknowledgments
Vulnerability CVE-2018-16864 was reported by Red Hat: https://access.redhat.com/security/cve/cve-2018-16864.
Vulnerability CVE-2018-16865 was reported by Red Hat: https://access.redhat.com/security/cve/cve-2018-16865.
Vulnerability CVE-2018-10897 was reported by Red Hat: https://access.redhat.com/security/cve/cve-2018-10897.
Vulnerability CVE-2018-6485 was reported by Red Hat: https://access.redhat.com/security/cve/cve-2018-6485.
Vulnerability CVE-2016-4463 was reported by Red Hat: https://access.redhat.com/security/cve/cve-2016-4463.
Vulnerability CVE-2018-0494 was reported by Red Hat: https://access.redhat.com/security/cve/cve-2018-0494.
Vulnerability CVE-2018-18311 was reported by Red Hat: https://access.redhat.com/security/cve/cve-2018-18311.
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: |
CVE-2018-16864: Stack overflow
CVE-2018-16865: Stack overflow CVE-2018-10897: Directory traversal CVE-2018-6485: Integer overflow CVE-2016-4463: Stack overflow CVE-2018-0494: Improper input validation CVE-2018-18311: Buffer overflow |
CVE ID:
|
CVE-2018-16864
CVE-2018-16865 CVE-2018-10897 CVE-2018-6485 CVE-2016-4463 CVE-2018-0494 CVE-2018-18311 |
Severity Rating: |
CVE-2018-16864: Medium
CVE-2018-16865: High CVE-2018-10897: High CVE-2018-6485: Medium CVE-2016-4463: High CVE-2018-0494: High CVE-2018-18311: High |
CVSS v3 Base / Temporal Scores: |
CVE-2018-16864: 6.4 / 6.1
CVE-2018-16865: 7.5 / 7.2 CVE-2018-10897: 8.8 / 8.4 CVE-2018-6485: 5.3 / 5.1 CVE-2016-4463: 7.5 / 7.2 CVE-2018-0494: 7.1 / 6.8 CVE-2018-18311: 7.4 / 7.1 |
Recommendations: |
Install or update to Web Gateway (MWG) 7.7.2.20
Install or update to MWG 7.8.2.7 (main release) Install or update to MWG 8.1 (controlled release) |
Security Bulletin Replacement:
|
None
|
Affected Software: |
CVE-2018-16864: MWG 7.8.2 earlier than MWG 7.8.2.7, 8.x earlier than 8.1
CVE-2018-16865: MWG 7.8.2 earlier than MWG 7.8.2.7, 8.x earlier than 8.1 CVE-2018-10897: MWG 7.7.2 earlier than MWG 7.7.2.20, 7.8.2 earlier than 7.8.2.7, 8.x earlier than 8.1 CVE-2018-6485: MWG 7.7.2, 7.8.2 earlier than 7.8.2.7, 8.x earlier than 8.1 CVE-2016-4463: MWG 7.7.2 earlier than MWG 7.7.2.20, 7.8.2 earlier than 7.8.2.7, 8.x earlier than 8.1 CVE-2018-0494: MWG 7.7.2 earlier than MWG 7.7.2.20, 7.8.2 earlier than 7.8.2.7, 8.x earlier than 8.1 CVE-2018-18311: MWG 7.7.2, 7.8.2 earlier than 7.8.2.7, 8.x earlier than 8.1 |
Location of updated software:
|
MWG 7.7.2.20 includes the fix for CVE-2018-15473 that was addressed previously in 7.8 and 8.0, and is described in SB10267. CVE-2018-16395 from the same Security Bulletin does not apply to 7.7.2.x.
MWG 7.7.2.20 does not include the fix for CVE-2018-18311 and CVE-2018-6485.
Article contents:
- Vulnerability Description
- Remediation
- Workaround
- Acknowledgments
- Frequently Asked Questions (FAQs)
- Resources
- Disclaimer
These vulnerabilities were reported against the Open Source operating system that MWG runs on:
- CVE-2018-16864:
An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when a program with long command line arguments calls syslog. A local attacker may use this flaw to crash systemd-journald or escalate privileges.
https://nvd.nist.gov/vuln/detail/CVE-2018-16864
- CVE-2018-16865:
An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when many entries are sent to the journal socket. A local attacker, or a remote one if systemd-journal-remote is used, may use this flaw to crash systemd-journald or execute code with journald privileges.
https://nvd.nist.gov/vuln/detail/CVE-2018-16865
- CVE-2018-10897:
A directory traversal issue was found in reposync, a part of yum-utils, where reposync fails to sanitize paths in remote repository configuration files. If an attacker controls a repository, they may be able to copy files outside of the destination directory on the targeted system via path traversal.
https://nvd.nist.gov/vuln/detail/CVE-2018-10897
- CVE-2018-6485:
An integer overflow in the implementation of the posix_memalign in memalign functions in the GNU C Library (aka glibc or libc6) 2.26 and earlier could cause these functions to return a pointer to a heap area that is too small, potentially leading to heap corruption. The packet update fixes other CVEs that are not exploitable (CVE-2017-16997, CVE-2018-11236, and CVE-2018-11237).
https://nvd.nist.gov/vuln/detail/CVE-2018-6485
- CVE-2016-4463:
A stack exhaustion flaw was found in the way Xerces-C XML parser handled deeply nested DTDs. An attacker could potentially use this flaw to crash an application.
https://nvd.nist.gov/vuln/detail/CVE-2018-4463
- CVE-2018-0494:
A cookie injection flaw was found in wget. An attacker can create a malicious website which, when accessed, overrides cookies belonging to arbitrary domains.
https://nvd.nist.gov/vuln/detail/CVE-2018-0494
- CVE-2018-18311:
Perl before 5.26.3 and 5.28.x before 5.28.1 has a buffer overflow via a crafted regular expression that triggers invalid write operations.
https://nvd.nist.gov/vuln/detail/CVE-2018-18311
- Other updated third-party libraries
The curl package was updated to cover 5 vulnerabilities (CVE-2018-1000007, CVE-2018-1000120, CVE-2018-1000121, CVE-2018-1000122, and CVE-2018-1000301). The highest CVSS3 score among these is 6.5.
The python package was updated to cover 2 vulnerabilities (CVE-2018-1060 and CVE-2018-1061). The highest CVSS3 score among these is 6.5.
To remediate this issue, go to the Product Downloads site, and download the applicable product update file:
Product | Version | Type | File Name | Release Date |
MWG | 7.7.2.20 | Main Release | mwgappl-7.7.2.20.0-28223-x.86_64.iso | March 12, 2019 |
MWG | 7.8.2.7 | Main Release | mwgappl-7.8.2.7.0-28225-x.86_64.iso | March 12, 2019 |
MWG | 8.1 | Controlled Release | mwgappl-8.1.0-28227x.86_64.iso | March 12, 2019 |
Download and Installation Instructions
All documentation and software relating to this and other MWG releases can be found on the Content & Cloud Security Portal.
Workaround
None.
Acknowledgments
Vulnerability CVE-2018-16864 was reported by Red Hat: https://access.redhat.com/security/cve/cve-2018-16864.
Vulnerability CVE-2018-16865 was reported by Red Hat: https://access.redhat.com/security/cve/cve-2018-16865.
Vulnerability CVE-2018-10897 was reported by Red Hat: https://access.redhat.com/security/cve/cve-2018-10897.
Vulnerability CVE-2018-6485 was reported by Red Hat: https://access.redhat.com/security/cve/cve-2018-6485.
Vulnerability CVE-2016-4463 was reported by Red Hat: https://access.redhat.com/security/cve/cve-2016-4463.
Vulnerability CVE-2018-0494 was reported by Red Hat: https://access.redhat.com/security/cve/cve-2018-0494.
Vulnerability CVE-2018-18311 was reported by Red Hat: https://access.redhat.com/security/cve/cve-2018-18311.
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-16864: system infinite memory allocation
Base Score 6.4 Attack Vector (AV) Local (L) Attack Complexity (AC) High (H) Privileges Required (PR) High (H) User Interaction (UI) None (N) Scope (S) Unchanged (U) Confidentiality (C) High (H) Integrity (I) High (H) Availability (A) High (H) Temporal Score (Overall) 6.1 Exploitability (E) Not Defined (X) 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:H/PR:H/UI:N/S:U/C:H/I:H/A:H/RL:O
- CVE-2018-16865: system infinite memory allocation
Base Score 7.5 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) High (H) Integrity (I) High (H) Availability (A) High (H) Temporal Score (Overall) 7.2 Exploitability (E) Not Defined (X) 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:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/RL:O
- CVE-2018-10897: Directory traversal in yum-utils
Base Score 8.8 Attack Vector (AV) Network (N) Attack Complexity (AC) Low (L) Privileges Required (PR) None (N) User Interaction (UI) Required (R) Scope (S) Unchanged (U) Confidentiality (C) High (H) Integrity (I) High (H) Availability (A) High (H) Temporal Score (Overall) 8.4 Exploitability (E) Not Defined (X) 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:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/RL:O
- CVE-2018-6485: Integer overflow in glibc
Base Score 5.3 Attack Vector (AV) Local (L) 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) Not Defined (X) 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:L/UI:N/S:U/C:L/I:L/A:L/RL:O
- CVE-2016-4463: Stack overflow in Xerces-C
Base Score 7.5 Attack Vector (AV) Network (N) Attack Complexity (AC) Low (L) 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) 7.2 Exploitability (E) Not Defined (X) 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:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/RL:O
- CVE-2018-0494: wget: Cookie injection
Base Score 7.1 Attack Vector (AV) Network (N) Attack Complexity (AC) Low (L) Privileges Required (PR) Low (L) User Interaction (UI) Required (R) Scope (S) Unchanged (U) Confidentiality (C) High (H) Integrity (I) Low (L) Availability (A) None (N) Temporal Score (Overall) 6.8 Exploitability (E) Not Defined (X) 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:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N/RL:O
- CVE-2018-18311: perl: Buffer overflow
Base Score 7.4 Attack Vector (AV) Local (L) Attack Complexity (AC) High (H) Privileges Required (PR) None (N) User Interaction (UI) None (R) Scope (S) Unchanged (U) Confidentiality (C) High (H) Integrity (I) High (H) Availability (A) High (H) Temporal Score (Overall) 7.1 Exploitability (E) Not Defined (X) 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:H/PR:N/UI:N/S:U/C:H/I:H/A:H/RL:O
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.