Security Bulletin - OpenSSL update for vulnerabilities CVE-2017-3735, CVE-2017-3736, CVE-2017-3737, and CVE-2017-3738
Security Bulletins ID:
SB10220
Last Modified: 2022-05-04 15:19:06 Etc/GMT
Last Modified: 2022-05-04 15:19:06 Etc/GMT
Summary
First Published: December 21, 2017
CVE Information | ||||
CVE Numbers | Severity Rating | CVSS v3 Base Scores | Affected Products | |
CVE-2017-3735 | Medium | Base 5.3 Overall 4.6 |
Advanced Threat Defense (ATD) 3.6, 3.8, 3.10, 4.0 Data Exchange Layer (DXL) Broker 4.0.0 Web Gateway 7.7.2.x, 7.8.0.x Network Data Loss Prevention (NDLP) Monitor 11.x NDLP Prevent 10.x, 11.x Network Security Platform (NSP) Sensor 8.x, 9.x Network Threat Behavior Analysis (NTBA) Appliance 8.x, 9.x Security Information Event Management (SIEM) 9.6.x, 10.x Threat Intelligence Exchange (TIE) Server 1.2.1, 1.3.0, 2.0.0, 2.0.1, 2.1.0, 2.1.1 |
|
Medium | Base 5.3 Overall 5.3 |
Email Gateway 7.x | ||
CVE-2017-3736 | Medium | Base 5.9 Overall 5.0 |
ATD 3.6, 3.8, 3.10, 4.0 DXL Broker 4.0.0 NDLP Monitor 11.x NDLP Prevent 10.x, 11.x NSP Sensor 8.x, 9.x NTBA Appliance 8.x, 9.x SIEM 9.6.x, 10.x TIE Server 1.2.1, 1.3.0, 2.0.0, 2.0.1, 2.1.0, 2.1.1 |
|
Medium | Base 5.9 Overall 5.9 |
Email Gateway 7.x | ||
Medium | Base 5.9 Overall 4.9 |
Web Gateway 7.7.2.x, 7.8.0.x | ||
CVE-2017-3737 | Medium | Base 6.4 Overall 5.4 |
ATD 3.6, 3.8, 3.10, 4.0 NTBA Appliance 8.x, 9.x TIE Server 1.2.1, 1.3.0, 2.0.0, 2.0.1, 2.1.0, 2.1.1 |
|
Medium | Base 5.9 Overall 5.9 |
Email Gateway 7.x NDLP Monitor 11.x NDLP Prevent 10.x, 11.x |
||
CVE-2017-3738 | Medium | Base 6.5 Overall 5.4 |
NTBA Appliance 8.x, 9.x | |
Medium | Base 5.9 Overall 5.9 |
Email Gateway 7.x NDLP Montior 11.x NDLP Prevent 10.x, 11.x |
||
Recommendations: | See the Remediation section of this Security Bulletin | |||
Security Bulletin Replacement: | None | |||
Affected Software: | See the Product Vulnerability Status lists below | |||
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:
Description
This OpenSSL update resolves the following vulnerabilities.
CVE-2017-3735
While parsing an IPAddressFamily extension in an X.509 certificate, it is possible to do a one-byte overread. This would result in an incorrect text display of the certificate. This bug has been present since 2006 and is present in all versions of OpenSSL before 1.0.2m and 1.1.0g.
https://nvd.nist.gov/vuln/detail/CVE-2017-3735
CVE-2017-3736
There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL before 1.0.2m and 1.1.0 before 1.1.0g. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would also need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. This only affects processors that support the BMI1, BMI2, and ADX extensions like Intel Broadwell (5th generation) and later or AMD Ryzen.
https://nvd.nist.gov/vuln/detail/CVE-2017-3736
CVE-2017-3737
OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error state" mechanism. The intent was that if a fatal error occurred during a handshake then OpenSSL would move into the error state and would immediately fail if you attempted to continue the handshake. This works as designed for the explicit handshake functions (SSL_do_handshake(), SSL_accept(), and SSL_connect()); however, due to a bug it does not work correctly if SSL_read() or SSL_write() is called directly. In that scenario, if the handshake fails then a fatal error will be returned in the initial function call. If SSL_read()/SSL_write() is subsequently called by the application for the same SSL object, then it will succeed and the data is passed without being decrypted/encrypted directly from the SSL/TLS record layer. To exploit this issue, an application bug would have to be present that resulted in a call to SSL_read()/SSL_write() being issued after having already received a fatal error. OpenSSL version 1.0.2b-1.0.2m are affected. Fixed in OpenSSL 1.0.2n. OpenSSL 1.1.0 is not affected.
https://nvd.nist.gov/vuln/detail/CVE-2017-3737
CVE-2017-3738
There is an overflow bug in the AVX2 Montgomery multiplication procedure used in exponentiation with 1024-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH1024 are considered just feasible, because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be significant. However, for an attack on TLS to be meaningful, the server would have to share the DH1024 private key among multiple clients, which is no longer an option since CVE-2016-0701. This only affects processors that support the AVX2 but not ADX extensions like Intel Haswell (4th generation). The impact from this issue is similar to CVE-2017-3736, CVE-2017-3732, and CVE-2015-3193. OpenSSL version 1.0.2-1.0.2m and 1.1.0-1.1.0g are affected. Fixed in OpenSSL 1.0.2n.
https://nvd.nist.gov/vuln/detail/CVE-2017-3738
CVE-2017-3735
While parsing an IPAddressFamily extension in an X.509 certificate, it is possible to do a one-byte overread. This would result in an incorrect text display of the certificate. This bug has been present since 2006 and is present in all versions of OpenSSL before 1.0.2m and 1.1.0g.
https://nvd.nist.gov/vuln/detail/CVE-2017-3735
CVE-2017-3736
There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL before 1.0.2m and 1.1.0 before 1.1.0g. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would also need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. This only affects processors that support the BMI1, BMI2, and ADX extensions like Intel Broadwell (5th generation) and later or AMD Ryzen.
https://nvd.nist.gov/vuln/detail/CVE-2017-3736
CVE-2017-3737
OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error state" mechanism. The intent was that if a fatal error occurred during a handshake then OpenSSL would move into the error state and would immediately fail if you attempted to continue the handshake. This works as designed for the explicit handshake functions (SSL_do_handshake(), SSL_accept(), and SSL_connect()); however, due to a bug it does not work correctly if SSL_read() or SSL_write() is called directly. In that scenario, if the handshake fails then a fatal error will be returned in the initial function call. If SSL_read()/SSL_write() is subsequently called by the application for the same SSL object, then it will succeed and the data is passed without being decrypted/encrypted directly from the SSL/TLS record layer. To exploit this issue, an application bug would have to be present that resulted in a call to SSL_read()/SSL_write() being issued after having already received a fatal error. OpenSSL version 1.0.2b-1.0.2m are affected. Fixed in OpenSSL 1.0.2n. OpenSSL 1.1.0 is not affected.
https://nvd.nist.gov/vuln/detail/CVE-2017-3737
CVE-2017-3738
There is an overflow bug in the AVX2 Montgomery multiplication procedure used in exponentiation with 1024-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH1024 are considered just feasible, because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be significant. However, for an attack on TLS to be meaningful, the server would have to share the DH1024 private key among multiple clients, which is no longer an option since CVE-2016-0701. This only affects processors that support the AVX2 but not ADX extensions like Intel Haswell (4th generation). The impact from this issue is similar to CVE-2017-3736, CVE-2017-3732, and CVE-2015-3193. OpenSSL version 1.0.2-1.0.2m and 1.1.0-1.1.0g are affected. Fixed in OpenSSL 1.0.2n.
https://nvd.nist.gov/vuln/detail/CVE-2017-3738
Product Vulnerability Status
Investigation into our products is ongoing. This Security Bulletin will be updated as additional information is available.
Investigation into our products is ongoing. This Security Bulletin will be updated as additional information is available.
Vulnerable and Updated
- ATD 3.6, 3.8, 3.10, 4.0
- DXL Broker 4.0.0
McAfee Active Response (MAR) 2.x - Email Gateway 7.x
- Web Gateway 7.7.2.x, 7.8.0.x
- NDLP Monitor 11.x
- NDLP Prevent 10.x, 11.x
- NSP Sensor 8.x, 9.x
- NTBA Appliance 8.x, 9.x
- SaaS Email Protection and Continuity (SaaS Email)
- SIEM 9.6.x, 10.x
- TIE Server 1.x, 2.x
VirusScan Enterprise for Linux (VSEL) 1.x, 2.x
ePolicy Orchestrator (ePO) 5.x- VirusScan Enterprise (VSE) for Windows 8.8
Remediation
Go to the Product Downloads site and download the applicable product update or hotfix files:
Product | Type | Name | Release Date |
ATD 3.x, 4.0 (includes vATD) | Feature Release | Advanced Threat Defense (ATD and vATD) 4.2 | November 30, 2017 |
DXL Broker | Hotfix | DXL 4.0.0 Hotfix 2 | November 21, 2017 |
MAR 2.x | Hotfix | MAR-Server-Bundle_2.3.0_Build_171_(ENU-RELEASE-MAIN).zip | September 4, 2018 |
Email Gateway 7.x | Hotfix | MEG-7.6.406h1252891-3484.101.zip | September 20, 2018 |
Web Gateway 7.7.2.7 or later | Maintenance Release | mwgappl-7.7.2.7.0-24770.x86_64.iso | November 29, 2017 |
Web Gateway 7.8.0.2 or later | Feature Release | mwgappl-7.7.2.7.0-24770.x86_64.iso | November 29, 2017 |
NDLP Monitor 11.x | Update | McAfee-MS-11.0.301-3487.102.iso | July 10, 2018 |
NDLP Prevent 10.x | Update | McAfee-PS-10.0.301-3466.102.iso | December 14, 2017 |
NDLP Prevent 11.x | Update | McAfee-PS-11.0.301-3487.102.iso | July 10, 2018 |
NSP 8.1.3.135 | 8.1 hotfix release for M-series hardware | 8.1 HF patched with OpenSSL v1.0.2m | February 21, 2018 |
NSP 8.1.5.217 | 8.1 hotfix release for NS-series hardware | 8.1 HF patched with OpenSSL v1.0.2m | February 12, 2018 |
NSP 8.3.5.48 | 8.3 hotfix release for NS-series hardware | 8.3 HF patched with OpenSSL v1.0.2m | December 7, 2017 |
NSP 9.1.5.19 | 9.1 hotfix release for NS-7x50 hardware only | 9.1 HF patched with OpenSSL v1.0.2m | December 12, 2017 |
NSP 9.1.5.20 | 9.1 Maintenance Release for NS-9x00, NS7x00, NS-7x00, and NS-3000 hardware appliances and all 9.1 virtual machine images | 9.1 MR1 patched with OpenSSL v1.0.2m | December 13, 2017 |
NTBA 8.1.3.42 | 8.1 hotfix release for NTBA physical appliance and virtual machines | NTBA 8.1.3.42 patched with OpenSSL v1.0.2n | January 24, 2018 |
NTBA 8.3.4.65 | 8.3 hotfix release for NTBA physical appliance and virtual machines | NTBA 8.3.4.65 patched with OpenSSL v1.0.2n | January 5, 2018 |
NTBA 9.1.3.8 | 9.1 hotfix release for NTBA physical appliance and virtual machines | NTBA 9.1.3.8 patched with OpenSSL v1.0.2n | January 18, 2018 |
SIEM 9.6.x, 10.x | Update | SIEM 10.2.0 | November 21, 2017 |
TIE Server 1.2.1, 1.3.0, 2.0.0, 2.0.1, 2.1.0, 2.1.1 | Hotfix | TIE Server 2.1.1 Hotfix 2 | March 1, 2018 |
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
Web Gateway:
For additional information, see SB10211. The affected Web Gateway software versions are:
For additional information, see SB10211. The affected Web Gateway software versions are:
- Web Gateway 7.6 until and including 7.6.2.17
- Web Gateway 7.7 until and including 7.7.2.6
- Web Gateway 7.8 until and including 7.8.0.1
Mitigations
None. We recommend upgrading to the versions specified in the Remediation table.
Frequently Asked Questions (FAQs)
How do I know whether my product is vulnerable?
For Endpoint products:
Use the following instructions for endpoint or client-based products:
Check the version and build of ePO that is installed. For information about how to check the version, see KB52634.
For Appliances:
Use the following instructions for Appliance-based products: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, 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 successful exploitation of the issue being scored
What are the CVSS scoring metrics that have been used?
CVE-2017-3735 - ATD, DXL, Web Gateway, NDLP, NSP, NTBA, SIEM, TIE Server: Malformed X.509 IPAddressFamily could cause OOB read
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:L/A:N/E:P/RL:T/RC:R
CVE-2017-3736 - ATD, DXL Broker, NDLP, NSP Sensor, SIEM, TIE Server: bn_sqrx8x_internal carry bug on x86_64
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:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:T/RC:R
CVE-2017-3737 - ATD, NTBA, TIE Server: SSL_read()/SSL_write() issued directly after fatal error in SSL handshake leads to unencrypted transfer of data
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:N/UI:R/S:U/C:H/I:L/A:L/E:U/RL:O/RC:R
CVE-2017-3737 - NDLP: SSL_read()/SSL_write() issued directly after fatal error in SSL handshake leads to unencrypted transfer of data
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:N/UI:N/S:U/C:H/I:N/A:N
CVE-2017-3738 - NTBA: overflow bug in multiplication procedure used in exponentiation with 1024-bit moduli
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:N/UI:N/S:U/C:H/I:N/A:L/E:U/RL:O/RC:R
CVE-2017-3738 - NDLP: overflow bug in multiplication procedure used in exponentiation with 1024-bit moduli
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:N/UI:N/S:U/C:H/I:N/A:N
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.
For Endpoint products:
Use the following instructions for endpoint or client-based products:
- Right-click on the McAfee tray shield icon on the Windows taskbar.
- Select Open Console.
- In the console, select Action Menu.
- In the Action Menu, select Product Details. The product version is displayed.
Check the version and build of ePO that is installed. For information about how to check the version, see KB52634.
For Appliances:
Use the following instructions for Appliance-based products:
- Open the Administrator's User Interface (UI).
- Click the About link. The product version is displayed.
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 successful exploitation of the issue being scored
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) | None (N) |
Integrity (I) | Low (L) |
Availability (A) | None (N) |
Temporal Score (Overall) | 4.6 |
Exploitability (E) | Proof-of-Concept (P) |
Remediation Level (RL) | Temporary Fix (T) |
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:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:P/RL:T/RC:R
CVE-2017-3736 - ATD, DXL Broker, NDLP, NSP Sensor, SIEM, TIE Server: bn_sqrx8x_internal carry bug on x86_64
Base Score | 5.9 |
Attack Vector (AV) | Network (N) |
Attack Complexity (AC) | High (H) |
Privileges Required (PR) | None (N) |
User Interaction (UI) | None (N) |
Scope (S) | Unchanged (U) |
Confidentiality (C) | High (H) |
Integrity (I) | None (N) |
Availability (A) | None (N) |
Temporal Score (Overall) | 5.0 |
Exploitability (E) | Unproven (U) |
Remediation Level (RL) | Temporary Fix (T) |
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:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:T/RC:R
CVE-2017-3737 - ATD, NTBA, TIE Server: SSL_read()/SSL_write() issued directly after fatal error in SSL handshake leads to unencrypted transfer of data
Base Score | 6.4 |
Attack Vector (AV) | Network (N) |
Attack Complexity (AC) | High (H) |
Privileges Required (PR) | None (N) |
User Interaction (UI) | Required (R) |
Scope (S) | Unchanged (C) |
Confidentiality (C) | High (H) |
Integrity (I) | Low (L) |
Availability (A) | Low (L) |
Temporal Score (Overall) | 5.4 |
Exploitability (E) | Unproven (F) |
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:N/UI:R/S:U/C:H/I:L/A:L/E:U/RL:O/RC:R
CVE-2017-3737 - NDLP: SSL_read()/SSL_write() issued directly after fatal error in SSL handshake leads to unencrypted transfer of data
Base Score | 5.9 |
Attack Vector (AV) | Network (N) |
Attack Complexity (AC) | High (H) |
Privileges Required (PR) | None (N) |
User Interaction (UI) | None (N) |
Scope (S) | Unchanged (C) |
Confidentiality (C) | High (H) |
Integrity (I) | None (N) |
Availability (A) | None (N) |
Temporal Score (Overall) | 5.9 |
Exploitability (E) | Not Defined |
Remediation Level (RL) | Not Defined |
Report Confidence (RC) | Not Defined |
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:N/UI:N/S:U/C:H/I:N/A:N
CVE-2017-3738 - NTBA: overflow bug in multiplication procedure used in exponentiation with 1024-bit moduli
Base Score | 6.5 |
Attack Vector (AV) | Network (N) |
Attack Complexity (AC) | High (H) |
Privileges Required (PR) | None (N) |
User Interaction (UI) | None (N) |
Scope (S) | Unchanged (U) |
Confidentiality (C) | High (H) |
Integrity (I) | None (N) |
Availability (A) | Low (L) |
Temporal Score (Overall) | 5.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:N/UI:N/S:U/C:H/I:N/A:L/E:U/RL:O/RC:R
CVE-2017-3738 - NDLP: overflow bug in multiplication procedure used in exponentiation with 1024-bit moduli
Base Score | 5.9 |
Attack Vector (AV) | Network (N) |
Attack Complexity (AC) | High (H) |
Privileges Required (PR) | None (N) |
User Interaction (UI) | None (N) |
Scope (S) | Unchanged (U) |
Confidentiality (C) | High (H) |
Integrity (I) | None (N) |
Availability (A) | None (N) |
Temporal Score (Overall) | 5.9 |
Exploitability (E) | Not Defined |
Remediation Level (RL) | Not Defined |
Report Confidence (RC) | Not Defined |
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:N/UI:N/S:U/C:H/I:N/A:N
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.
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.