CVE-2022-394: Malicious code in @logistics-frontend/modules (npm)
Summary
MAL-2022-394: Malicious code in @logistics-frontend/modules (npm). Affected versions are not published. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The @logistics-frontend/modules package is an npm package that provides modules for logistics-related frontend applications. It is commonly used to handle various logistics operations such as tracking, shipping, and inventory management. This package is vulnerable to a malicious code injection attack, which can compromise the security of any system that has it installed.
Vulnerability Detail
The vulnerability, identified as CVE-2022-394, originates from the presence of malicious code in the @logistics-frontend/modules package. This code can fully compromise any computer that has the package installed or running. As a result, all secrets and keys stored on the affected computer should be rotated immediately from a different computer. While removing the package is recommended, it may not guarantee the removal of all malicious software installed as a result of its presence.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @logistics-frontend/modulesIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no specific workaround available for this vulnerability. It is essential to follow the recommended steps for fixing the issue and ensuring the security of the system.
Conclusion
The presence of malicious code in the @logistics-frontend/modules package poses a significant security risk to any system that has it installed. It is crucial to follow the recommended steps for fixing the vulnerability, including rotating secrets and keys, removing the package, conducting a security audit, and monitoring the system for any suspicious activities. For additional support and guidance, please contact DevNack.com.
See every vulnerability recorded for @logistics-frontend/modules →
FAQ
The impact of this vulnerability is severe as it can fully compromise the security of any system that has the @logistics-frontend/modules package installed. It can lead to unauthorized access, data breaches, and potential loss of sensitive information.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply provide the package-lock.json file, and Vulert will analyze it in real-time to identify any open-source vulnerabilities.
While removing the @logistics-frontend/modules package is recommended, it may not guarantee the complete removal of all malicious software resulting from its presence. It is crucial to follow the recommended steps for fixing the vulnerability and conducting a thorough security audit.
As this vulnerability involves malicious code injection, there is a potential for various exploits. It is essential to address the vulnerability promptly and monitor the system for any suspicious activities.
For further support and assistance in vulnerability remediation, you can reach out to info@devnack.com. They can provide guidance and help ensure the security of your system.
