3KXG200000R4801
Vulnerability from csaf_abb - Published: 2025-04-16 00:30 - Updated: 2025-10-20 00:30Summary
CoreSense™ HM and CoreSense™ M10 File Path Traversal Vulnerability
Notes
Summary
An update is available that resolves vulnerability in the product versions listed as affected in this advisory.
A path traversal vulnerability in these products can allow unauthenticated users to gain access to restricted directories. Exploiting this vulnerability can lead to complete system compromise and exposure of sensitive information.
General security recommendations
For any installation of software-related ABB products we strongly recommend the following (non-exhaustive) list of cyber security practices:
– Isolate special purpose networks (e.g. for automation systems) and remote devices behind firewalls and separate them from any general-purpose network (e.g. office or home networks).
– Install physical controls so no unauthorized personnel can access your devices, components, peripheral equipment, and networks.
– Never connect programming software or computers containing programing software to any network other than the network for the devices that it is intended for.
– Scan all data imported into your environment before use to detect potential malware infections.
– Minimize network exposure for all applications and endpoints to ensure that they are not accessible from the Internet unless they are designed for such exposure and the intended use requires such.
– 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.
– When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Recognize that VPNs may have vulnerabilities and should be updated to the most current version available. Also, understand that VPNs are only as secure as the connected devices.
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 damage 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 damage.
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.
Mitigating factors
The path traversal vulnerability is only exploitable when the attacker has local access to the machine hosting the web application (i.e., access to localhost). To mitigate this vulnerability, the affected products should be configured to restrict local access to authorized users only, ensuring that untrusted users cannot interact with the application directly on the host system.
ABB has restricted file downloads to a specific directory designated solely for downloadable content. Strict input validation and path sanitization are implemented to ensure that only legitimate file paths within this directory can be accessed.
Refer to section “General Security Recommendations” for further advise on how to keep your system secure.
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.
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 causes the vulnerability?
The vulnerability is caused by unchecked input data in the file parameter in the CoreSense products.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability can allow unauthenticated users to gain access to restricted directories and can lead to complete system compromise and exposure of sensitive information.
How could an attacker exploit the vulnerability?
Path traversal would require that the attacker has access to the system local network, by connecting to the system directly or through a wrongly configured or penetrated firewall, or that he installs malicious software on a system node or otherwise infects the network with malicious software.
Recommended practices help mitigate such attacks, see section Mitigating Factors above.
Could the vulnerability be exploited remotely?
No.
Can functional safety be affected by an exploit of this vulnerability?
No.
What does the update do?
The update removes the vulnerability by modifying the way that the file parameter validates and verifies input data.
When this security advisory was issued, had this vulnerability been publicly disclosed?
No, ABB received information about this vulnerability through responsible disclosure.
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 this vulnerability had been exploited when this security advisory was originally issued.
{
"document": {
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"text": "\u00a9 Copyright 2025 ABB. All rights reserved.",
"tlp": {
"label": "WHITE"
}
},
"lang": "en",
"notes": [
{
"category": "summary",
"text": "An update is available that resolves vulnerability in the product versions listed as affected in this advisory.\n\nA path traversal vulnerability in these products can allow unauthenticated users to gain access to restricted directories. Exploiting this vulnerability can lead to complete system compromise and exposure of sensitive information.",
"title": "Summary"
},
{
"category": "other",
"text": "For any installation of software-related ABB products we strongly recommend the following (non-exhaustive) list of cyber security practices:\n\n\u2013 Isolate special purpose networks (e.g. for automation systems) and remote devices behind firewalls and separate them from any general-purpose network (e.g. office or home networks).\n\n\u2013 Install physical controls so no unauthorized personnel can access your devices, components, peripheral equipment, and networks.\n\n\u2013 Never connect programming software or computers containing programing software to any network other than the network for the devices that it is intended for.\n\n\u2013 Scan all data imported into your environment before use to detect potential malware infections.\n\n\u2013 Minimize network exposure for all applications and endpoints to ensure that they are not accessible from the Internet unless they are designed for such exposure and the intended use requires such.\n\n\u2013 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\n\u2013 When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Recognize that VPNs may have vulnerabilities and should be updated to the most current version available. Also, understand that VPNs are only as secure as the connected devices.",
"title": "General security recommendations"
},
{
"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 damage 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 damage. \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": "general",
"text": "The path traversal vulnerability is only exploitable when the attacker has local access to the machine hosting the web application (i.e., access to localhost). To mitigate this vulnerability, the affected products should be configured to restrict local access to authorized users only, ensuring that untrusted users cannot interact with the application directly on the host system.\n\nABB has restricted file downloads to a specific directory designated solely for downloadable content. Strict input validation and path sanitization are implemented to ensure that only legitimate file paths within this directory can be accessed. \n\nRefer to section \u201cGeneral Security Recommendations\u201d for further advise on how to keep your system secure.\n",
"title": "Mitigating factors"
},
{
"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.\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 causes the vulnerability?\n\nThe vulnerability is caused by unchecked input data in the file parameter in the CoreSense products.\n\nWhat might an attacker use the vulnerability to do?\n\nAn attacker who successfully exploited this vulnerability can allow unauthenticated users to gain access to restricted directories and can lead to complete system compromise and exposure of sensitive information.\n\nHow could an attacker exploit the vulnerability?\n\nPath traversal would require that the attacker has access to the system local network, by connecting to the system directly or through a wrongly configured or penetrated firewall, or that he installs malicious software on a system node or otherwise infects the network with malicious software. \n\nRecommended practices help mitigate such attacks, see section Mitigating Factors above.\n\nCould the vulnerability be exploited remotely? \n\nNo.\n\nCan functional safety be affected by an exploit of this vulnerability?\n\nNo.\n\nWhat does the update do?\n\nThe update removes the vulnerability by modifying the way that the file parameter validates and verifies input data. \n\nWhen this security advisory was issued, had this vulnerability been publicly disclosed?\n\nNo, ABB received information about this vulnerability through responsible disclosure.\n\nWhen this security advisory was issued, had ABB received any reports that this vulnerability was being exploited?\n\nNo, ABB had not received any information indicating that this vulnerability had been exploited when this security advisory was originally issued.",
"title": "Frequently Asked Questions"
}
],
"publisher": {
"category": "vendor",
"name": "ABB PSIRT",
"namespace": "https://global.abb/group/en/technology/cyber-security/alerts-and-notifications"
},
"references": [
{
"category": "self",
"summary": "ABB CYBERSECURITY ADVISORY - PDF version ",
"url": "https://search.abb.com/library/Download.aspx?DocumentID=3KXG200000R4801\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"category": "self",
"summary": "ABB CYBERSECURITY ADVISORY - CSAF version ",
"url": "https://psirt.abb.com/csaf/2025/3kxg200000r4801.json"
}
],
"title": "CoreSense\u2122 HM and CoreSense\u2122 M10 File Path Traversal Vulnerability",
"tracking": {
"current_release_date": "2025-10-20T00:30:00.000Z",
"generator": {
"date": "2025-10-14T06:37:03.454Z",
"engine": {
"name": "Secvisogram",
"version": "2.5.37"
}
},
"id": "3KXG200000R4801",
"initial_release_date": "2025-04-16T00:30:00.000Z",
"revision_history": [
{
"date": "2025-04-16T00:30:00.000Z",
"legacy_version": "A",
"number": "1",
"summary": "Initial version."
},
{
"date": "2025-09-30T00:30:00.000Z",
"legacy_version": "B",
"number": "2",
"summary": "Addressed comments."
},
{
"date": "2025-10-07T00:30:00.000Z",
"legacy_version": "C",
"number": "3",
"summary": "Fixed incorrect links."
},
{
"date": "2025-10-20T00:30:00.000Z",
"legacy_version": "D",
"number": "4",
"summary": "Final version with corrected dates."
}
],
"status": "final",
"version": "4"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version_range",
"name": "\u003c=2.3.1",
"product": {
"name": "CoreSense\u2122 HM\u003c=2.3.1",
"product_id": "AV1"
}
},
{
"category": "product_version",
"name": "2.3.4",
"product": {
"name": "CoreSense\u2122 HM 2.3.4",
"product_id": "FX1"
}
}
],
"category": "product_family",
"name": "CoreSense\u2122 HM"
},
{
"branches": [
{
"category": "product_version_range",
"name": "\u003c=1.4.1.12",
"product": {
"name": "CoreSense\u2122 M10\u003c=1.4.1.12",
"product_id": "AV2"
}
},
{
"category": "product_version",
"name": "1.4.1.31",
"product": {
"name": "CoreSense\u2122 M10 1.4.1.31",
"product_id": "FX2"
}
}
],
"category": "product_family",
"name": "CoreSense\u2122 M10"
}
],
"category": "vendor",
"name": "ABB"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2025-3465",
"cwe": {
"id": "CWE-22",
"name": "Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027)"
},
"notes": [
{
"category": "description",
"text": "A path traversal vulnerability in these products can allow unauthenticated users to gain access to restricted directories. Exploiting this vulnerability can lead to complete system compromise and exposure of sensitive information.",
"title": "CVE description"
}
],
"product_status": {
"fixed": [
"FX1",
"FX2"
],
"known_affected": [
"AV1",
"AV2"
]
},
"references": [
{
"category": "external",
"summary": "NVD - CVE-2025-3465",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-3465"
}
],
"remediations": [
{
"category": "vendor_fix",
"details": "The vulnerabilities are corrected in the following version: \n\nCoreSense\u2122 HM v2.3.4 \u0026 CoreSense\u2122 M10 v1.4.1.31\n\nABB recommends that customers apply the update at the earliest convenience.",
"product_ids": [
"AV1",
"AV2"
]
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"environmentalScore": 7.1,
"environmentalSeverity": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"temporalScore": 7.1,
"temporalSeverity": "HIGH",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N",
"version": "3.1"
},
"products": [
"AV1",
"AV2"
]
}
],
"title": "CVE-2025-3465"
}
]
}
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…