Information Disclosure vulnerabilities allow access to application configuration information. Affected products: ABB ASPECT - Enterprise v3…
Information Disclosure vulnerabilities allow access to application configuration information. Affected products: ABB ASPECT - Enterprise v3.08.02; NEXUS Series v3.08.02; MATRIX Series v3.08.02
One or more system settings or configuration elements can be externally controlled by a user.
https://cwe.mitre.org/data/definitions/15.html →Open in CWE collection →The adversary directly or indirectly modifies environment variables used by or controlling the target software. The adversary's goal is to cause the target software to deviate from its expected operation in a manner that benefits the adversary.
https://capec.mitre.org/data/definitions/13.html →Open in CAPEC collection →This attack targets programs running with elevated privileges. The adversary tries to leverage a vulnerability in the running program and get arbitrary code to execute with elevated privileges.
https://capec.mitre.org/data/definitions/69.html →Open in CAPEC collection →An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
https://capec.mitre.org/data/definitions/76.html →Open in CAPEC collection →This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An adversary can override variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the adversary can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.
https://capec.mitre.org/data/definitions/77.html →Open in CAPEC collection →An adversary corrupts or modifies the content of XML schema information passed between a client and server for the purpose of undermining the security of the target. XML Schemas provide the structure and content definitions for XML documents. Schema poisoning is the ability to manipulate a schema either by replacing or modifying it to compromise the programs that process documents that use this schema.
https://capec.mitre.org/data/definitions/146.html →Open in CAPEC collection →An attacker manipulates files or settings external to a target application which affect the behavior of that application. For example, many applications use external configuration files and libraries - modification of these entities or otherwise affecting the application's ability to use them would constitute a configuration/environment manipulation attack.
https://capec.mitre.org/data/definitions/176.html →Open in CAPEC collection →An adversary exploits a weakness in authorization in order to modify content within a registry (e.g., Windows Registry, Mac plist, application registry). Editing registry information can permit the adversary to hide configuration information or remove indicators of compromise to cover up activity. Many applications utilize registries to store configuration and service information. As such, modification of registry information can affect individual services (affecting billing, authorization, or even allowing for identity spoofing) or the overall configuration of a targeted application. For example, both Java RMI and SOAP use registries to track available services. Changing registry values is sometimes a preliminary step towards completing another attack pattern, but given the long term usage of many registry values, manipulation of registry information could be its own end.
https://capec.mitre.org/data/definitions/203.html →Open in CAPEC collection →An adversary adds a new entry to the "run keys" in the Windows registry so that an application of their choosing is executed when a user logs in. In this way, the adversary can get their executable to operate and run on the target system with the authorized user's level of permissions. This attack is a good way for an adversary to run persistent spyware on a user's machine, such as a keylogger.
https://capec.mitre.org/data/definitions/270.html →Open in CAPEC collection →An adversary corrupts or modifies the content of a schema for the purpose of undermining the security of the target. Schemas provide the structure and content definitions for resources used by an application. By replacing or modifying a schema, the adversary can affect how the application handles or interprets a resource, often leading to possible denial of service, entering into an unexpected state, or recording incomplete data.
https://capec.mitre.org/data/definitions/271.html →Open in CAPEC collection →Winlogon is a part of Windows that performs logon actions. In Windows systems prior to Windows Vista, a registry key can be modified that causes Winlogon to load a DLL on startup. Adversaries may take advantage of this feature to load adversarial code at startup.
https://capec.mitre.org/data/definitions/579.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| aspect-ent-12_firmware | * | Tracked |
| aspect-ent-256_firmware | * | Tracked |
| aspect-ent-2_firmware | * | Tracked |
| aspect-ent-96_firmware | * | Tracked |
| matrix-11_firmware | * | Tracked |
| matrix-216_firmware | * | Tracked |
| matrix-232_firmware | * | Tracked |
| matrix-264_firmware | * | Tracked |
| matrix-296_firmware | * | Tracked |
| nexus-2128-a_firmware | * | Tracked |
| nexus-2128-f_firmware | * | Tracked |
| nexus-2128-g_firmware | * | Tracked |
| nexus-2128_firmware | * | Tracked |
| nexus-264-a_firmware | * | Tracked |
| nexus-264-f_firmware | * | Tracked |
| nexus-264-g_firmware | * | Tracked |
| nexus-264_firmware | * | Tracked |
| nexus-3-2128_firmware | * | Tracked |
| nexus-3-264_firmware | * | Tracked |