An attacker could decipher the encryption and gain access to MDT AutoSave versions prior to v6.02.06.
Vendor
MDT Software vulnerabilities
7 published CVES affecting MDT Software, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 7
- Critical
- 2
- High
- 5
- Medium
- 0
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Products
Latest MDT Software CVEs
Newest publication first
-
HighCVSS 7.5 EPSS 0.41%
-
HighCVSS 7.5 EPSS 1.1%
An attacker could utilize a function in MDT AutoSave versions prior to v6.02.06 that permits changing a designated path to another path and traversing the directory, allowing the replacement of an existing file with a malicious file.
-
HighCVSS 7.5 EPSS 0.89%
A function in MDT AutoSave versions prior to v6.02.06 is used to retrieve system information for a specific process, and this information collection executes multiple commands and summarizes the information into an XML. This function and subsequent process gives full path to the...
-
HighCVSS 7.5 EPSS 1.1%
An attacker can gain knowledge of a session temporary working folder where the getfile and putfile commands are used in MDT AutoSave versions prior to v6.02.06. An attacker can leverage this knowledge to provide a malicious command to the working directory where the read and writ...
-
CriticalCVSS 9.8 EPSS 1.2%
An attacker could leverage an API to pass along a malicious file that could then manipulate the process creation command line in MDT AutoSave versions prior to v6.02.06 and run a command line argument. This could then be leveraged to run a malicious process.
-
CriticalCVSS 9.8 EPSS 1.2%
An attacker could utilize SQL commands to create a new user MDT AutoSave versions prior to v6.02.06 and update the user’s permissions, granting the attacker the ability to login.
-
HighCVSS 7.5 EPSS 1.3%
A getfile function in MDT AutoSave versions prior to v6.02.06 enables a user to supply an optional parameter, resulting in the processing of a request in a special manner. This can result in the execution of an unzip command and place a malicious .exe file in one of the locations...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.