Mohanl0L

Name of the Vulnerable Software and Affected Versions: Shenzhim AAPTJS version 1.3.1 Description: An issue was discovered in the add function that allows attackers to execute arbitrary code via the `filePath` parameter. Recommendations: For Shenzhim AAPTJS version 1.3.1, consider restricting access to the `add` function or avoid using the `filePath` parameter until a fix is available. At the moment, there is no information about a newer version that contains a fix for this issue.

Name of the Vulnerable Software and Affected Versions: aaptjs version 1.3.1 Description: An issue was discovered in the list function in shenzhim aaptjs, allowing attackers to execute arbitrary code via the `filePath` parameters. This issue affects the functionality of aaptjs, which is a node wrapper for aapt. Recommendations: For aaptjs version 1.3.1, consider restricting access to the list function until a patch is available. As a temporary workaround, avoid using the `filePath` parameters in the affected list function to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: aaptjs version 1.3.1 Description: An issue was discovered in the dump function in shenzhim aaptjs, allowing attackers to execute arbitrary code via the `filePath` parameters. aaptjs is a node wrapper for aapt. Recommendations: For version 1.3.1, consider restricting access to the dump function to minimize the risk of exploitation. As a temporary workaround, avoid using the `filePath` parameters in the affected function until a patch is available. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: shenzhim aaptjs version 1.3.1 Description: An issue was discovered in the `packageCmd` function, allowing attackers to execute arbitrary code via the `filePath` parameters. This issue affects the shenzhim aaptjs package, which is a node wrapper for aapt. Recommendations: For shenzhim aaptjs version 1.3.1, consider disabling the `packageCmd` function until a patch is available to prevent exploitation via the `filePath` parameters. Restrict access to the `filePath` parameters in the affected function to minimize the risk of arbitrary code execution. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: aaptjs version 1.3.1 Description: An issue was discovered in the remove function in shenzhim aaptjs, allowing attackers to execute arbitrary code via the `filePath` parameters. aaptjs is a node wrapper for aapt. Recommendations: For version 1.3.1, consider restricting access to the remove function until a patch is available. As a temporary workaround, avoid using the `filePath` parameters in the affected function to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: aaptjs version 1.3.1 Description: An issue was discovered in the crunch function in shenzhim aaptjs, allowing attackers to execute arbitrary code via the `filePath` parameters. This issue affects the aaptjs node wrapper for aapt. Recommendations: For aaptjs version 1.3.1, consider restricting access to the crunch function until a patch is available. As a temporary workaround, avoid using the `filePath` parameters in the affected function to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: aaptjs version 1.3.1 Description: An issue was discovered in the `singleCrunch` function, allowing attackers to execute arbitrary code via the `filePath` parameters. This issue affects the aaptjs package, which is a node wrapper for aapt. Recommendations: For aaptjs version 1.3.1, consider disabling the `singleCrunch` function as a temporary workaround until a patch is available. Restrict access to the `filePath` parameters in the affected function to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.