9AKK108471A3623
Vulnerability from csaf_abb - Published: 2025-07-03 00:30 - Updated: 2025-08-18 00:30Summary
RMC - 100 Vulnerabilities in web UI (REST Interface)
Notes
summary
ABB is aware of vulnerabilities in the product versions listed as affected in the advisory.
An attacker who successfully exploited these vulnerabilities could gain unauthenticated access to the MQTT configu-ration data (CVE-2025-6074), cause a DoS on the MQTT configuration web server (REST interface) (CVE-2025-6073, CVE-2025-6072), or decrypt encrypted MQTT broker credentials (CVE-2025-6071).
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 equip-ment, and networks.
– Never connect programming software or computers containing programing software to any net-work 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 damages of any nature or kind arising from the use of this document, or from the use of any hard-ware 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.
Mitigating factors
ABB recommends disabling the REST interface when not being used to configure the MQTT functionality. By default, the REST interface is disabled so no risk is present.
The RMC-100 is not intended for access over public networks such as the internet. An attacker would need to have access to the customer’s private control network to exploit this vulnerability. Proper network segmentation is rec-ommended.
Refer to section “General security recommendations” for further advise on how to keep your system secure.
{
"document": {
"acknowledgments": [
{
"names": [
"Vera Mens"
],
"organization": "Claroty Team82",
"summary": "helping to identify the vulnerabilities and protecting our customers"
}
],
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"tlp": {
"label": "WHITE"
}
},
"lang": "en",
"notes": [
{
"category": "summary",
"text": "ABB is aware of vulnerabilities in the product versions listed as affected in the advisory.\n\nAn attacker who successfully exploited these vulnerabilities could gain unauthenticated access to the MQTT configu-ration data (CVE-2025-6074), cause a DoS on the MQTT configuration web server (REST interface) (CVE-2025-6073, CVE-2025-6072), or decrypt encrypted MQTT broker credentials (CVE-2025-6071).",
"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\tIsolate 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\tInstall physical controls so no unauthorized personnel can access your devices, components, peripheral equip-ment, and networks.\n\n\u2013\tNever connect programming software or computers containing programing software to any net-work other than the network for the devices that it is intended for.\n\n\u2013\tScan all data imported into your environment before use to detect potential malware infections.\n\n\u2013\tMinimize 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\tEnsure 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\tWhen 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.\n",
"title": "General security recommendations"
},
{
"category": "other",
"text": "For additional instructions and support please contact your local ABB service organization. \nFor contact \ninformation, see www.abb.com/contactcenters.\n\nInformation about ABB\u2019s cyber security program and capabilities can be found at www.abb.com/cybersecurity.\n",
"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 hard-ware 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": "general",
"text": "ABB recommends disabling the REST interface when not being used to configure the MQTT functionality. By default, the REST interface is disabled so no risk is present.\n\nThe RMC-100 is not intended for access over public networks such as the internet. An attacker would need to have access to the customer\u2019s private control network to exploit this vulnerability. Proper network segmentation is rec-ommended. \n\nRefer to section \u201cGeneral security recommendations\u201d for further advise on how to keep your system secure.\n",
"title": "Mitigating factors"
}
],
"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=9AKK108471A3623\u0026LanguageCode=en\u0026DocumentPartId=PDF\u0026Action=Launch"
},
{
"category": "self",
"summary": "ABB CYBERSECURITY ADVISORY - CSAF version ",
"url": "https://psirt.abb.com/csaf/2025/9akk108471a3623.json"
}
],
"title": "RMC - 100 Vulnerabilities in web UI (REST Interface)",
"tracking": {
"current_release_date": "2025-08-18T00:30:00.000Z",
"generator": {
"date": "2025-09-23T11:47:33.214Z",
"engine": {
"name": "Secvisogram",
"version": "2.5.35"
}
},
"id": "9AKK108471A3623",
"initial_release_date": "2025-07-03T00:30:00.000Z",
"revision_history": [
{
"date": "2025-07-03T00:30:00.000Z",
"legacy_version": "A",
"number": "1",
"summary": "Initial version."
},
{
"date": "2025-08-18T00:30:00.000Z",
"legacy_version": "B",
"number": "2",
"summary": "Added information on the software customer packages that correct the reported issue."
}
],
"status": "final",
"version": "2"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version_range",
"name": "\u003e=2105457-043|\u003c=2105457-045",
"product": {
"name": "RMC-100 Version (\u003e=2105457-043|\u003c=2105457-045) ",
"product_id": "AV1"
}
},
{
"category": "product_version",
"name": "2105457-046",
"product": {
"name": "RMC-100 Version (2105457-046)",
"product_id": "FX1"
}
}
],
"category": "product_name",
"name": "RMC-100"
},
{
"branches": [
{
"category": "product_version_range",
"name": "\u003e=2106229-015|\u003c=2106229-016",
"product": {
"name": "RMC-100 LITE Version (\u003e=2106229-015|\u003c=2106229-016)",
"product_id": "AV2"
}
},
{
"category": "product_version",
"name": "2106229-018",
"product": {
"name": "RMC-100 LITE (2106229-018)",
"product_id": "FX2"
}
}
],
"category": "product_name",
"name": "RMC-100 LITE"
}
],
"category": "vendor",
"name": "ABB"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2025-6074",
"cwe": {
"id": "CWE-321",
"name": "Use of Hard-coded Cryptographic Key"
},
"notes": [
{
"category": "description",
"text": "When the REST interface is enabled by the user, and an attacker gains access to source code and control network, the attacker can bypass the REST interface authentication and gain access to MQTT configuration data.",
"title": "CVE description"
}
],
"product_status": {
"fixed": [
"FX1",
"FX2"
],
"known_affected": [
"AV1",
"AV2"
]
},
"references": [
{
"category": "external",
"summary": "NVD -CVE-2025-6074",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-6074"
}
],
"remediations": [
{
"category": "vendor_fix",
"details": "The problem is corrected in RMC-100\t\nversion (2105457-046) and \nRMC-100 LITE version (2106229-018)",
"product_ids": [
"AV1",
"AV2"
]
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"environmentalScore": 6,
"environmentalSeverity": "MEDIUM",
"exploitCodeMaturity": "FUNCTIONAL",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"remediationLevel": "OFFICIAL_FIX",
"scope": "UNCHANGED",
"temporalScore": 6,
"temporalSeverity": "MEDIUM",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N/E:F/RL:O",
"version": "3.1"
},
"products": [
"AV1",
"AV2"
]
}
],
"title": "CVE-2025-6074"
},
{
"cve": "CVE-2025-6073",
"cwe": {
"id": "CWE-121",
"name": "Stack-based Buffer Overflow"
},
"notes": [
{
"category": "description",
"text": "When the REST interface is enabled by the user, and an attacker gains access to the con-trol network, and user/password broker authentication is enabled, and CVE-2025-6074 is exploited, the attacker can overflow the buffer for username or password.",
"title": "CVE description"
}
],
"product_status": {
"fixed": [
"FX1",
"FX2"
],
"known_affected": [
"AV1",
"AV2"
]
},
"references": [
{
"category": "external",
"summary": "NVD -CVE-2025-6073",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-6073"
}
],
"remediations": [
{
"category": "vendor_fix",
"details": "The problem is corrected in RMC-100\t\nversion (2105457-046) and \nRMC-100 LITE version (2106229-018)",
"product_ids": [
"AV1",
"AV2"
]
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"environmentalScore": 6.7,
"environmentalSeverity": "MEDIUM",
"exploitCodeMaturity": "PROOF_OF_CONCEPT",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"remediationLevel": "OFFICIAL_FIX",
"scope": "UNCHANGED",
"temporalScore": 6.7,
"temporalSeverity": "MEDIUM",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O",
"version": "3.1"
},
"products": [
"AV1",
"AV2"
]
}
],
"title": "CVE-2025-6073"
},
{
"cve": "CVE-2025-6072",
"cwe": {
"id": "CWE-121",
"name": "Stack-based Buffer Overflow"
},
"notes": [
{
"category": "description",
"text": "When the REST interface is enabled by the user, and an attacker gains access to the con-trol network, and CVE-2025-6074 is exploited, the attacker can use the JSON configura-tion to overflow the date of expiration field.",
"title": "CVE description"
}
],
"product_status": {
"fixed": [
"FX1",
"FX2"
],
"known_affected": [
"AV1",
"AV2"
]
},
"references": [
{
"category": "external",
"summary": "NVD -CVE-2025-6072",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-6072"
}
],
"remediations": [
{
"category": "vendor_fix",
"details": "The problem is corrected in RMC-100\t\nversion (2105457-046) and \nRMC-100 LITE version (2106229-018)",
"product_ids": [
"AV1",
"AV2"
]
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"environmentalScore": 6.7,
"environmentalSeverity": "MEDIUM",
"exploitCodeMaturity": "PROOF_OF_CONCEPT",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"remediationLevel": "OFFICIAL_FIX",
"scope": "UNCHANGED",
"temporalScore": 6.7,
"temporalSeverity": "MEDIUM",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O",
"version": "3.1"
},
"products": [
"AV1",
"AV2"
]
}
],
"title": "CVE-2025-6072"
},
{
"cve": "CVE-2025-6071",
"cwe": {
"id": "CWE-321",
"name": "Use of Hard-coded Cryptographic Key"
},
"notes": [
{
"category": "description",
"text": "Attacker can gain access to salted information to decrypt MQTT information.",
"title": "CVE description"
}
],
"product_status": {
"fixed": [
"FX1",
"FX2"
],
"known_affected": [
"AV1",
"AV2"
]
},
"references": [
{
"category": "external",
"summary": "CVE-2025-6071",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-6071"
}
],
"remediations": [
{
"category": "vendor_fix",
"details": "The problem is corrected in RMC-100\t\nversion (2105457-046) and \nRMC-100 LITE version (2106229-018)",
"product_ids": [
"AV1",
"AV2"
]
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"environmentalScore": 5.3,
"environmentalSeverity": "MEDIUM",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"temporalScore": 5.3,
"temporalSeverity": "MEDIUM",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"products": [
"AV1",
"AV2"
]
}
],
"title": "CVE-2025-6071"
}
]
}
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…