7PAA017341
Vulnerability from csaf_abb - Published: 2026-04-13 00:30 - Updated: 2026-04-13 00:30Summary
PostgreSQL vulnerabilities in ABB Ability™ Symphony® Plus Engineering
Notes
Summary: ABB became aware of vulnerability in the products versions listed as affected in the advisory. The ABB S+ Engineering product versions are affected by vulnerabilities in PostgreSQL version 13.11 and earlier versions. If an attacker gains access to a site’s S+ Client Server network, they could exploit such vulnerabilities by executing arbitrary code and potentially compromising the entire system.
Support: For additional instructions and support please contact your local ABB service organization. For contact information, see www.abb.com/contactcenters.
Information about ABB’s cyber security program and capabilities can be found at www.abb.com/cybersecurity.
Notice: The information in this document is subject to change without notice, and should not be construed as a commitment by ABB.
ABB provides no warranty, express or implied, including warranties of merchantability and fitness for a particular purpose, for the information contained in this document, and assumes no responsibility for any errors that may appear in this document. In no event shall ABB or any of its suppliers be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, or from the use of any hardware or software described in this document, even if ABB or its suppliers have been advised of the possibility of such damages.
This document and parts hereof must not be reproduced or copied without written permission from ABB, and the contents hereof must not be imparted to a third party nor used for any unauthorized purpose.
All rights to registrations and trademarks reside with their respective owners.
General security recommendations: Control systems and the control network are exposed to cyber threats. In order to minimize these risks, the protective measures and best practices listed below are available in addition to other measures. ABB strongly recommends system integrators and asset owners to implement the measures they consider appropriate for their control system environment:
- Place control systems in a dedicated control network containing control systems only.
- Locate control networks and systems behind firewalls and separate them from any other networks like business networks and the Internet.
- Block any inbound Internet traffic destined for the control networks/systems. Place remote access systems used for remote control system access outside the control network.
- Limit outbound Internet traffic originating from control systems/networks as much as possible. If control systems must talk to the Internet, tailor firewall rules to required resources - allow only source IPs, destination IPs and services/destination ports which control systems definitely need to use for nor-mal control operation.
- If Internet access is required on occasion only, disable relevant firewall rules and enable them during the time window of required Internet access only. If supported by your firewall, define an expiry date and time for such rules – after the expiry date and time, the firewall will disable the rule automatically.
- Limit exposure of control networks/systems to internal systems. Tailor firewall rules allowing traffic from internal systems to control networks/systems to allow only source IPs, destination IPs and ser-vices/destination ports which are definitely required for normal control operation.
- Create strict firewall rules to filter malicious network traffic targeting control system vulnerabilities ("exploit traffic"). Exploit traffic may use network communication features like source routing, IP fragmentation and/or IP tunneling. If such features are not required for normal control operation, block them on your firewall.
- If supported by your firewall, apply additional filters to allowed traffic which provide protection for control networks/systems. Such filters are provided by advanced firewall features like Application Control and Anti-Virus.
- Use Intrusion Detection Systems (IDS) or Intrusion Preventions Systems (IPS) to detect/block control system-specific exploit traffic. Consider using IPS rules protecting against control system exploits.
- When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Please ensure that VPN solutions are updated to the most current version available.
- In case you want to filter internal control network traffic, consider using solutions supporting Intra-LAN traffic control like VLAN access control lists.
- Harden your control systems by enabling only the ports, services and software required for normal control operation. Disable all other ports and disable/uninstall all other services and software.
- If possible, limit the permissions of user accounts, software processes and devices to the permissions required for normal control operation.
- Use trusted, patched software and malware protection solutions. Interact with trusted web sites and trusted email attachments only.
- Ensure all nodes are always up to date in terms of installed software, operating system and firmware patches as well as anti-virus and firewall.
- Protect control systems from physical access by unauthorized personnel e.g. by placing them in locked switch cabinets.
For more information on recommended practices can be found in the following documents Please refer to the reference section.
- 8VZZ001006T0001
- 2PAA121027
- 8VZZ000602
- 7PAA018617
- 2PAA122516
- 2PAA120528
- 8VZZ000368D0066
Purpose: ABB has a rigorous internal cyber security continuous improvement process which involves regular testing with industry leading tools and periodic assessments to identify potential product issues. Occasionally an issue is determined to be a design or coding flaw with implications that may impact product cyber security.
When a potential product vulnerability is identified or reported, ABB immediately initiates our vulnerability handling process. This entails validating if the issue is in fact a product issue, identifying root causes, determining what related products may be impacted, developing a remediation, and notifying end users and governmental organizations (e.g. ICS-CERT).
The resulting Cyber Security Advisory intends to notify customers of the vulnerability and provide details on which products are impacted, how to mitigate the vulnerability or explain workarounds that minimize the potential risk as much as possible. The release of a Cyber Security Advisory should not be misconstrued as an affirmation or indication of an active threat or ongoing campaign targeting the products mentioned here. If ABB is aware of any specific threats, it will be clearly mentioned in the communication.
The publication of this Cyber Security Advisory is an example of ABB’s commitment to the user community in support of this critical topic. Responsible disclosure is an important element in the chain of trust we work to maintain with our many customers. The release of an Advisory provides timely information which is essential to help ensure our customers are fully informed.
Frequently Asked Questions: What is the scope of the vulnerability?
- An attacker who successfully exploited these vulnerabilities could insert and run arbitrary code in the S+ system.
What causes the vulnerability?
- It is caused by several vulnerabilities in the PostgreSQL version 13.11 and earlier versions component used by the S+ Engineering product (see Affected products).
What might an attacker use the vulnerability to do?
- An attacker who successfully accessed the site’s S+ client/server network could cause a denial-of-service situation, corruptions of data or unauthorized disclosure of information.
How could an attacker exploit the vulnerability?
- To exploit the PostgreSQL vulnerabilities (see Vulnerability severity and details), an attacker should successfully access to the site’s S+ client/server network, remotely (through a wrongly configured or penetrated firewall) or even compromising a local machine and then accessing to PostgreSQL.
Recommended practices help mitigate such attacks, see section Mitigating Factors above.
Could the vulnerability be exploited remotely?
- Yes, see the above How could an attacker exploit the vulnerability?
Recommended practices include that process control systems are physically protected, have no direct connections to the Internet, and are separated from other networks by means of a firewall system that has a minimal number of ports exposed.
Can functional safety be affected by an exploit of this vulnerability?
- Functional safety systems are not affected by these vulnerabilities
What does the update do?
- The S+ Engineering update removes the vulnerability by installing a secure updated PostgreSQL version.
When this security advisory was issued, had this vulnerability been publicly disclosed?
- Yes, PostgreSQL 13.11 vulnerabilities have been publicly disclosed.
When this security advisory was issued, had ABB received any reports that this vulnerability was being exploited?
- No, ABB had not received any information indicating that S+ Engineering had been exploited when this security advisory was originally issued.
An attacker running as an authenticated PostgreSQL user can provide crafted data and trigger the integer overflow due to such missing overflow check. This can enable the execution of arbitrary code in the system.
CWE-190 - Integer Overflow or Wraparound
Vendor Fix
ABB advises all customers to review their installations to determine if they are using an impacted product as listed above, no further analysis or tools are needed to make this determination.
The recommended immediate actions per product are listed below:
- Systems using S+ Engineering 2.2 through 2.4 SP2 should upgrade to S+ Engineering 2.4 SP2 RU1 (re-leased in December 2024) or later.
- End users who are unable to install one of these updates should immediately look to implement the Mitigation and Workarounds listed below as this will restrict or prevent an attacker’s ability to com-promise the system.
ABB recommends that customers apply the update at the earliest convenience.
Mitigation
Any exploit of these vulnerabilities would require that the attacker has access to the site’s S+ client/server network. Following ABB’s recommended security practices, including network architecture and perimeter firewall, are mitigating factors in preventing external access to the S+ client/server net-work.
Refer to section “General security recommendations” for further advise on how to keep your system secure.
Workaround
No workarounds are available. Assess the installation specific risk based on this advisory. Use the recommendations described under “Mitigating factors” or “Recommended immediate actions”.
If an administrator has installed Extension scripts and specific data is used inside a quoting con-struct, an attacker having proper PostgreSQL privileges can execute arbitrary code in the system as the administrator.
CWE-89 - Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Vendor Fix
ABB advises all customers to review their installations to determine if they are using an impacted product as listed above, no further analysis or tools are needed to make this determination.
The recommended immediate actions per product are listed below:
- Systems using S+ Engineering 2.2 through 2.4 SP2 should upgrade to S+ Engineering 2.4 SP2 RU1 (re-leased in December 2024) or later.
- End users who are unable to install one of these updates should immediately look to implement the Mitigation and Workarounds listed below as this will restrict or prevent an attacker’s ability to com-promise the system.
ABB recommends that customers apply the update at the earliest convenience.
Mitigation
Any exploit of these vulnerabilities would require that the attacker has access to the site’s S+ client/server network. Following ABB’s recommended security practices, including network architecture and perimeter firewall, are mitigating factors in preventing external access to the S+ client/server net-work.
Refer to section “General security recommendations” for further advise on how to keep your system secure.
Workaround
No workarounds are available. Assess the installation specific risk based on this advisory. Use the recommendations described under “Mitigating factors” or “Recommended immediate actions”.
A ‘time-of-check time-of-use’ (TOCTOU) race condition in a PostgreSQL can allow an attacker to easily execute arbitrary SQL functions by leveraging a PostgreSQL utility often executed with high privileges.
CWE-367 - Time-of-check Time-of-use (TOCTOU) Race Condition
Vendor Fix
ABB advises all customers to review their installations to determine if they are using an impacted product as listed above, no further analysis or tools are needed to make this determination.
The recommended immediate actions per product are listed below:
- Systems using S+ Engineering 2.2 through 2.4 SP2 should upgrade to S+ Engineering 2.4 SP2 RU1 (re-leased in December 2024) or later.
- End users who are unable to install one of these updates should immediately look to implement the Mitigation and Workarounds listed below as this will restrict or prevent an attacker’s ability to com-promise the system.
ABB recommends that customers apply the update at the earliest convenience.
Mitigation
Any exploit of these vulnerabilities would require that the attacker has access to the site’s S+ client/server network. Following ABB’s recommended security practices, including network architecture and perimeter firewall, are mitigating factors in preventing external access to the S+ client/server net-work.
Refer to section “General security recommendations” for further advise on how to keep your system secure.
Workaround
No workarounds are available. Assess the installation specific risk based on this advisory. Use the recommendations described under “Mitigating factors” or “Recommended immediate actions”.
An attacker can provide untrusted materialized views and lure a high privileged authorized user to inadvertently execute arbitrary SQL functions by refreshing the attacker's materialized view.
CWE-271 - Privilege Dropping / Lowering Errors
Vendor Fix
ABB advises all customers to review their installations to determine if they are using an impacted product as listed above, no further analysis or tools are needed to make this determination.
The recommended immediate actions per product are listed below:
- Systems using S+ Engineering 2.2 through 2.4 SP2 should upgrade to S+ Engineering 2.4 SP2 RU1 (re-leased in December 2024) or later.
- End users who are unable to install one of these updates should immediately look to implement the Mitigation and Workarounds listed below as this will restrict or prevent an attacker’s ability to com-promise the system.
ABB recommends that customers apply the update at the earliest convenience.
Mitigation
Any exploit of these vulnerabilities would require that the attacker has access to the site’s S+ client/server network. Following ABB’s recommended security practices, including network architecture and perimeter firewall, are mitigating factors in preventing external access to the S+ client/server net-work.
Refer to section “General security recommendations” for further advise on how to keep your system secure.
Workaround
No workarounds are available. Assess the installation specific risk based on this advisory. Use the recommendations described under “Mitigating factors” or “Recommended immediate actions”.
References
{
"document": {
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"tlp": {
"label": "WHITE"
}
},
"lang": "en",
"notes": [
{
"category": "summary",
"text": "ABB became aware of vulnerability in the products versions listed as affected in the advisory. The ABB S+ Engineering product versions are affected by vulnerabilities in PostgreSQL version 13.11 and earlier versions. If an attacker gains access to a site\u2019s S+ Client Server network, they could exploit such vulnerabilities by executing arbitrary code and potentially compromising the entire system.",
"title": "Summary"
},
{
"category": "other",
"text": "For additional instructions and support please contact your local ABB service organization. For contact information, see www.abb.com/contactcenters.\n\nInformation about ABB\u2019s cyber security program and capabilities can be found at www.abb.com/cybersecurity.",
"title": "Support"
},
{
"category": "legal_disclaimer",
"text": "The information in this document is subject to change without notice, and should not be construed as a commitment by ABB.\n\nABB provides no warranty, express or implied, including warranties of merchantability and fitness for a particular purpose, for the information contained in this document, and assumes no responsibility for any errors that may appear in this document. In no event shall ABB or any of its suppliers be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, or from the use of any hardware or software described in this document, even if ABB or its suppliers have been advised of the possibility of such damages.\n\nThis document and parts hereof must not be reproduced or copied without written permission from ABB, and the contents hereof must not be imparted to a third party nor used for any unauthorized purpose.\n\nAll rights to registrations and trademarks reside with their respective owners.\n",
"title": "Notice"
},
{
"category": "other",
"text": "Control systems and the control network are exposed to cyber threats. In order to minimize these risks, the protective measures and best practices listed below are available in addition to other measures. ABB strongly recommends system integrators and asset owners to implement the measures they consider appropriate for their control system environment:\n\n- Place control systems in a dedicated control network containing control systems only.\n- Locate control networks and systems behind firewalls and separate them from any other networks like business networks and the Internet.\n- Block any inbound Internet traffic destined for the control networks/systems. Place remote access systems used for remote control system access outside the control network.\n- Limit outbound Internet traffic originating from control systems/networks as much as possible. If control systems must talk to the Internet, tailor firewall rules to required resources - allow only source IPs, destination IPs and services/destination ports which control systems definitely need to use for nor-mal control operation.\n- If Internet access is required on occasion only, disable relevant firewall rules and enable them during the time window of required Internet access only. If supported by your firewall, define an expiry date and time for such rules \u2013 after the expiry date and time, the firewall will disable the rule automatically.\n- Limit exposure of control networks/systems to internal systems. Tailor firewall rules allowing traffic from internal systems to control networks/systems to allow only source IPs, destination IPs and ser-vices/destination ports which are definitely required for normal control operation.\n- Create strict firewall rules to filter malicious network traffic targeting control system vulnerabilities (\"exploit traffic\"). Exploit traffic may use network communication features like source routing, IP fragmentation and/or IP tunneling. If such features are not required for normal control operation, block them on your firewall.\n- If supported by your firewall, apply additional filters to allowed traffic which provide protection for control networks/systems. Such filters are provided by advanced firewall features like Application Control and Anti-Virus.\n- Use Intrusion Detection Systems (IDS) or Intrusion Preventions Systems (IPS) to detect/block control system-specific exploit traffic. Consider using IPS rules protecting against control system exploits.\n- When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Please ensure that VPN solutions are updated to the most current version available.\n- In case you want to filter internal control network traffic, consider using solutions supporting Intra-LAN traffic control like VLAN access control lists.\n- Harden your control systems by enabling only the ports, services and software required for normal control operation. Disable all other ports and disable/uninstall all other services and software.\n- If possible, limit the permissions of user accounts, software processes and devices to the permissions required for normal control operation.\n- Use trusted, patched software and malware protection solutions. Interact with trusted web sites and trusted email attachments only.\n- Ensure all nodes are always up to date in terms of installed software, operating system and firmware patches as well as anti-virus and firewall.\n- Protect control systems from physical access by unauthorized personnel e.g. by placing them in locked switch cabinets.\n\nFor more information on recommended practices can be found in the following documents Please refer to the reference section.\n- 8VZZ001006T0001\n- 2PAA121027\n- 8VZZ000602\n- 7PAA018617\n- 2PAA122516\n- 2PAA120528\n- 8VZZ000368D0066",
"title": "General security recommendations"
},
{
"category": "other",
"text": "ABB has a rigorous internal cyber security continuous improvement process which involves regular testing with industry leading tools and periodic assessments to identify potential product issues. Occasionally an issue is determined to be a design or coding flaw with implications that may impact product cyber security.\n\nWhen a potential product vulnerability is identified or reported, ABB immediately initiates our vulnerability handling process. This entails validating if the issue is in fact a product issue, identifying root causes, determining what related products may be impacted, developing a remediation, and notifying end users and governmental organizations (e.g. ICS-CERT).\n\nThe resulting Cyber Security Advisory intends to notify customers of the vulnerability and provide details on which products are impacted, how to mitigate the vulnerability or explain workarounds that minimize the potential risk as much as possible. The release of a Cyber Security Advisory should not be misconstrued as an affirmation or indication of an active threat or ongoing campaign targeting the products mentioned here. If ABB is aware of any specific threats, it will be clearly mentioned in the communication.\n\nThe publication of this Cyber Security Advisory is an example of ABB\u2019s commitment to the user community in support of this critical topic. Responsible disclosure is an important element in the chain of trust we work to maintain with our many customers. The release of an Advisory provides timely information which is essential to help ensure our customers are fully informed.",
"title": "Purpose"
},
{
"category": "faq",
"text": "What is the scope of the vulnerability?\n- An attacker who successfully exploited these vulnerabilities could insert and run arbitrary code in the S+ system. \n\nWhat causes the vulnerability?\n- It is caused by several vulnerabilities in the PostgreSQL version 13.11 and earlier versions component used by the S+ Engineering product (see Affected products).\n\nWhat might an attacker use the vulnerability to do?\n- An attacker who successfully accessed the site\u2019s S+ client/server network could cause a denial-of-service situation, corruptions of data or unauthorized disclosure of information.\n\nHow could an attacker exploit the vulnerability?\n- To exploit the PostgreSQL vulnerabilities (see Vulnerability severity and details), an attacker should successfully access to the site\u2019s S+ client/server network, remotely (through a wrongly configured or penetrated firewall) or even compromising a local machine and then accessing to PostgreSQL.\n\n Recommended practices help mitigate such attacks, see section Mitigating Factors above.\n\nCould the vulnerability be exploited remotely? \n- Yes, see the above How could an attacker exploit the vulnerability? \nRecommended practices include that process control systems are physically protected, have no direct connections to the Internet, and are separated from other networks by means of a firewall system that has a minimal number of ports exposed.\n\nCan functional safety be affected by an exploit of this vulnerability?\n- Functional safety systems are not affected by these vulnerabilities\n\nWhat does the update do?\n- The S+ Engineering update removes the vulnerability by installing a secure updated PostgreSQL version.\n\nWhen this security advisory was issued, had this vulnerability been publicly disclosed?\n- Yes, PostgreSQL 13.11 vulnerabilities have been publicly disclosed.\n\nWhen this security advisory was issued, had ABB received any reports that this vulnerability was being exploited?\n- No, ABB had not received any information indicating that S+ Engineering had been exploited when this security advisory was originally issued.",
"title": "Frequently Asked Questions"
}
],
"publisher": {
"category": "vendor",
"name": "ABB PSIRT",
"namespace": "https://www.abb.com/global/en/company/about/cybersecurity/alerts-and-notifications"
},
"references": [
{
"category": "self",
"summary": "ABB CYBERSECURITY ADVISORY - PDF Version ",
"url": "https://search.abb.com/library/Download.aspx?DocumentID=7PAA017341\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"category": "self",
"summary": "ABB CYBERSECURITY ADVISORY - CSAF Version ",
"url": "https://psirt.abb.com/csaf/2026/7paa017341.json"
},
{
"summary": "7PAA014844D2421 : S+ Engineering 2.4 SP2 Rollup 1 Release notes ",
"url": "https://search.abb.com/library/Download.aspx?DocumentID=7PAA014844D2421\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"summary": "8VZZ001006T0001 : Symphony Plus Secure deployment guide for Windows 10 and Server 2016/2019 User manual ",
"url": "https://search.abb.com/library/Download.aspx?DocumentID=8VZZ001006T0001\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"summary": "2PAA121027 : Distributed Control Systems Trellix ePO with Endpoint Security and Application Control - Configuration Manual ",
"url": "https://search.abb.com/library/Download.aspx?DocumentID=2PAA121027\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"summary": "8VZZ000602 : Symphony Plus Security Updates Validation Status ",
"url": "https://search.abb.com/library/Download.aspx?DocumentID=8VZZ000602T0001\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"summary": "7PAA018617 : Symphony Plus Daily Validation of Anti-Malware Definition Updates ",
"url": "https://search.abb.com/library/Download.aspx?DocumentID=7PAA018617\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"summary": "2PAA122516 : System 800xA, Symphony Plus and Freelance - System Hardening - End user manual ",
"url": "https://search.abb.com/library/Download.aspx?DocumentID=2PAA122516\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"summary": "2PAA120528 : System 800xA, Symphony Plus and Freelance - System Hardening - Group Policies Overview ",
"url": "https://search.abb.com/library/Download.aspx?DocumentID=2PAA120528\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"summary": "8VZZ000368D0066 : ABB ICS Cyber Security Reference Architecture - Document ",
"url": "https://search.abb.com/library/Download.aspx?DocumentID=8VZZ000368D0066\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
}
],
"title": "PostgreSQL vulnerabilities in ABB Ability\u2122 Symphony\u00ae Plus Engineering",
"tracking": {
"current_release_date": "2026-04-13T00:30:00.000Z",
"generator": {
"date": "2026-04-13T05:41:09.523Z",
"engine": {
"name": "Secvisogram",
"version": "2.5.47"
}
},
"id": "7PAA017341",
"initial_release_date": "2026-04-13T00:30:00.000Z",
"revision_history": [
{
"date": "2026-04-13T00:30:00.000Z",
"legacy_version": "A",
"number": "1",
"summary": "Initial version."
}
],
"status": "final",
"version": "1"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version",
"name": "2.2",
"product": {
"name": "ABB Ability\u2122 Symphony\u00ae Plus S+ Engineering 2.2",
"product_id": "AV1"
}
},
{
"category": "product_version",
"name": "2.3",
"product": {
"name": "ABB Ability\u2122 Symphony\u00ae Plus S+ Engineering 2.3",
"product_id": "AV2"
}
},
{
"category": "product_version",
"name": "2.3 RU1",
"product": {
"name": "ABB Ability\u2122 Symphony\u00ae Plus S+ Engineering 2.3 RU1",
"product_id": "AV3"
}
},
{
"category": "product_version",
"name": "2.3 RU2",
"product": {
"name": "ABB Ability\u2122 Symphony\u00ae Plus S+ Engineering 2.3 RU2",
"product_id": "AV4"
}
},
{
"category": "product_version",
"name": "2.3 RU3",
"product": {
"name": "ABB Ability\u2122 Symphony\u00ae Plus S+ Engineering 2.3 RU3",
"product_id": "AV5"
}
},
{
"category": "product_version",
"name": "2.4",
"product": {
"name": "ABB Ability\u2122 Symphony\u00ae Plus S+ Engineering 2.4",
"product_id": "AV6"
}
},
{
"category": "product_version",
"name": "2.4 SP1",
"product": {
"name": "ABB Ability\u2122 Symphony\u00ae Plus S+ Engineering 2.4 SP1",
"product_id": "AV7"
}
},
{
"category": "product_version",
"name": "2.4 SP2",
"product": {
"name": "ABB Ability\u2122 Symphony\u00ae Plus S+ Engineering 2.4 SP2",
"product_id": "AV8"
}
},
{
"category": "product_version",
"name": "2.4 SP2 RU1",
"product": {
"name": "ABB Ability\u2122 Symphony\u00ae Plus S+ Engineering 2.4 SP2 RU1",
"product_id": "FX1"
}
}
],
"category": "product_name",
"name": "S+ Engineering "
}
],
"category": "product_family",
"name": "Ability\u2122 Symphony\u00ae Plus"
}
],
"category": "vendor",
"name": "ABB"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2023-5869",
"cwe": {
"id": "CWE-190",
"name": "Integer Overflow or Wraparound"
},
"notes": [
{
"category": "description",
"text": "An attacker running as an authenticated PostgreSQL user can provide crafted data and trigger the integer overflow due to such missing overflow check. This can enable the execution of arbitrary code in the system.",
"title": "CVE description"
}
],
"product_status": {
"fixed": [
"FX1"
],
"known_affected": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
},
"references": [
{
"category": "external",
"summary": "NVD - CVE-2023-5869",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-5869"
}
],
"remediations": [
{
"category": "vendor_fix",
"details": "ABB advises all customers to review their installations to determine if they are using an impacted product as listed above, no further analysis or tools are needed to make this determination. \n\nThe recommended immediate actions per product are listed below:\n- Systems using S+ Engineering 2.2 through 2.4 SP2 should upgrade to S+ Engineering 2.4 SP2 RU1 (re-leased in December 2024) or later. \n- End users who are unable to install one of these updates should immediately look to implement the Mitigation and Workarounds listed below as this will restrict or prevent an attacker\u2019s ability to com-promise the system.\n\nABB recommends that customers apply the update at the earliest convenience.\n",
"product_ids": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
},
{
"category": "mitigation",
"details": "Any exploit of these vulnerabilities would require that the attacker has access to the site\u2019s S+ client/server network. Following ABB\u2019s recommended security practices, including network architecture and perimeter firewall, are mitigating factors in preventing external access to the S+ client/server net-work. \n\nRefer to section \u201cGeneral security recommendations\u201d for further advise on how to keep your system secure.\n",
"product_ids": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
},
{
"category": "workaround",
"details": "No workarounds are available. Assess the installation specific risk based on this advisory. Use the recommendations described under \u201cMitigating factors\u201d or \u201cRecommended immediate actions\u201d.",
"product_ids": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"environmentalScore": 8.6,
"environmentalSeverity": "HIGH",
"exploitCodeMaturity": "FUNCTIONAL",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"remediationLevel": "UNAVAILABLE",
"reportConfidence": "CONFIRMED",
"scope": "UNCHANGED",
"temporalScore": 8.6,
"temporalSeverity": "HIGH",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:U/RC:C",
"version": "3.1"
},
"products": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
}
],
"title": "CVE-2023-5869"
},
{
"cve": "CVE-2023-39417",
"cwe": {
"id": "CWE-89",
"name": "Improper Neutralization of Special Elements used in an SQL Command (\u0027SQL Injection\u0027)"
},
"notes": [
{
"category": "description",
"text": "If an administrator has installed Extension scripts and specific data is used inside a quoting con-struct, an attacker having proper PostgreSQL privileges can execute arbitrary code in the system as the administrator.",
"title": "CVE description"
}
],
"product_status": {
"fixed": [
"FX1"
],
"known_affected": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
},
"references": [
{
"category": "external",
"summary": "NVD - CVE-2023-39417",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-39417"
}
],
"remediations": [
{
"category": "vendor_fix",
"details": "ABB advises all customers to review their installations to determine if they are using an impacted product as listed above, no further analysis or tools are needed to make this determination. \n\nThe recommended immediate actions per product are listed below:\n- Systems using S+ Engineering 2.2 through 2.4 SP2 should upgrade to S+ Engineering 2.4 SP2 RU1 (re-leased in December 2024) or later. \n- End users who are unable to install one of these updates should immediately look to implement the Mitigation and Workarounds listed below as this will restrict or prevent an attacker\u2019s ability to com-promise the system.\n\nABB recommends that customers apply the update at the earliest convenience.\n",
"product_ids": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
},
{
"category": "mitigation",
"details": "Any exploit of these vulnerabilities would require that the attacker has access to the site\u2019s S+ client/server network. Following ABB\u2019s recommended security practices, including network architecture and perimeter firewall, are mitigating factors in preventing external access to the S+ client/server net-work. \n\nRefer to section \u201cGeneral security recommendations\u201d for further advise on how to keep your system secure.\n",
"product_ids": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
},
{
"category": "workaround",
"details": "No workarounds are available. Assess the installation specific risk based on this advisory. Use the recommendations described under \u201cMitigating factors\u201d or \u201cRecommended immediate actions\u201d.",
"product_ids": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"environmentalScore": 7.3,
"environmentalSeverity": "HIGH",
"exploitCodeMaturity": "FUNCTIONAL",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"remediationLevel": "UNAVAILABLE",
"reportConfidence": "CONFIRMED",
"scope": "UNCHANGED",
"temporalScore": 7.3,
"temporalSeverity": "HIGH",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:U/RC:C",
"version": "3.1"
},
"products": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
}
],
"title": "CVE-2023-39417"
},
{
"cve": "CVE-2024-7348",
"cwe": {
"id": "CWE-367",
"name": "Time-of-check Time-of-use (TOCTOU) Race Condition"
},
"notes": [
{
"category": "description",
"text": "A \u2018time-of-check time-of-use\u2019 (TOCTOU) race condition in a PostgreSQL can allow an attacker to easily execute arbitrary SQL functions by leveraging a PostgreSQL utility often executed with high privileges.",
"title": "CVE description"
}
],
"product_status": {
"fixed": [
"FX1"
],
"known_affected": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
},
"references": [
{
"category": "external",
"summary": "NVD - CVE-2024-7348",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-7348"
}
],
"remediations": [
{
"category": "vendor_fix",
"details": "ABB advises all customers to review their installations to determine if they are using an impacted product as listed above, no further analysis or tools are needed to make this determination. \n\nThe recommended immediate actions per product are listed below:\n- Systems using S+ Engineering 2.2 through 2.4 SP2 should upgrade to S+ Engineering 2.4 SP2 RU1 (re-leased in December 2024) or later. \n- End users who are unable to install one of these updates should immediately look to implement the Mitigation and Workarounds listed below as this will restrict or prevent an attacker\u2019s ability to com-promise the system.\n\nABB recommends that customers apply the update at the earliest convenience.\n",
"product_ids": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
},
{
"category": "mitigation",
"details": "Any exploit of these vulnerabilities would require that the attacker has access to the site\u2019s S+ client/server network. Following ABB\u2019s recommended security practices, including network architecture and perimeter firewall, are mitigating factors in preventing external access to the S+ client/server net-work. \n\nRefer to section \u201cGeneral security recommendations\u201d for further advise on how to keep your system secure.\n",
"product_ids": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
},
{
"category": "workaround",
"details": "No workarounds are available. Assess the installation specific risk based on this advisory. Use the recommendations described under \u201cMitigating factors\u201d or \u201cRecommended immediate actions\u201d.",
"product_ids": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"environmentalScore": 8.6,
"environmentalSeverity": "HIGH",
"exploitCodeMaturity": "FUNCTIONAL",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"remediationLevel": "UNAVAILABLE",
"reportConfidence": "CONFIRMED",
"scope": "UNCHANGED",
"temporalScore": 8.6,
"temporalSeverity": "HIGH",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:U/RC:C",
"version": "3.1"
},
"products": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
}
],
"title": "CVE-2024-7348"
},
{
"cve": "CVE-2024-0985",
"cwe": {
"id": "CWE-271",
"name": "Privilege Dropping / Lowering Errors"
},
"notes": [
{
"category": "description",
"text": "An attacker can provide untrusted materialized views and lure a high privileged authorized user to inadvertently execute arbitrary SQL functions by refreshing the attacker\u0027s materialized view.",
"title": "CVE description"
}
],
"product_status": {
"fixed": [
"FX1"
],
"known_affected": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
},
"references": [
{
"category": "external",
"summary": "NVD - CVE-2024-0985",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-0985"
}
],
"remediations": [
{
"category": "vendor_fix",
"details": "ABB advises all customers to review their installations to determine if they are using an impacted product as listed above, no further analysis or tools are needed to make this determination. \n\nThe recommended immediate actions per product are listed below:\n- Systems using S+ Engineering 2.2 through 2.4 SP2 should upgrade to S+ Engineering 2.4 SP2 RU1 (re-leased in December 2024) or later. \n- End users who are unable to install one of these updates should immediately look to implement the Mitigation and Workarounds listed below as this will restrict or prevent an attacker\u2019s ability to com-promise the system.\n\nABB recommends that customers apply the update at the earliest convenience.\n",
"product_ids": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
},
{
"category": "mitigation",
"details": "Any exploit of these vulnerabilities would require that the attacker has access to the site\u2019s S+ client/server network. Following ABB\u2019s recommended security practices, including network architecture and perimeter firewall, are mitigating factors in preventing external access to the S+ client/server net-work. \n\nRefer to section \u201cGeneral security recommendations\u201d for further advise on how to keep your system secure.\n",
"product_ids": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
},
{
"category": "workaround",
"details": "No workarounds are available. Assess the installation specific risk based on this advisory. Use the recommendations described under \u201cMitigating factors\u201d or \u201cRecommended immediate actions\u201d.",
"product_ids": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"environmentalScore": 7.8,
"environmentalSeverity": "HIGH",
"exploitCodeMaturity": "FUNCTIONAL",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"remediationLevel": "UNAVAILABLE",
"reportConfidence": "CONFIRMED",
"scope": "UNCHANGED",
"temporalScore": 7.8,
"temporalSeverity": "HIGH",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:F/RL:U/RC:C",
"version": "3.1"
},
"products": [
"AV1",
"AV2",
"AV3",
"AV4",
"AV5",
"AV6",
"AV7",
"AV8"
]
}
],
"title": "CVE-2024-0985"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…