Verax NMS prior to 2.1.0 uses an encryption key that is hardcoded in a JAR archive.
References
| Link | Resource |
|---|---|
| http://www.securityfocus.com/bid/58334 | Third Party Advisory VDB Entry |
| https://exchange.xforce.ibmcloud.com/vulnerabilities/82706 | Third Party Advisory VDB Entry |
| https://packetstormsecurity.com/files/cve/CVE-2013-1352/page1/ | Third Party Advisory VDB Entry |
| http://www.securityfocus.com/bid/58334 | Third Party Advisory VDB Entry |
| https://exchange.xforce.ibmcloud.com/vulnerabilities/82706 | Third Party Advisory VDB Entry |
| https://packetstormsecurity.com/files/cve/CVE-2013-1352/page1/ | Third Party Advisory VDB Entry |
Configurations
History
21 Nov 2024, 01:49
| Type | Values Removed | Values Added |
|---|---|---|
| References | () http://www.securityfocus.com/bid/58334 - Third Party Advisory, VDB Entry | |
| References | () https://exchange.xforce.ibmcloud.com/vulnerabilities/82706 - Third Party Advisory, VDB Entry | |
| References | () https://packetstormsecurity.com/files/cve/CVE-2013-1352/page1/ - Third Party Advisory, VDB Entry |
Information
Published : 2020-01-30 14:15
Updated : 2024-11-21 01:49
NVD link : CVE-2013-1352
Mitre link : CVE-2013-1352
CVE.ORG link : CVE-2013-1352
JSON object : View
Products Affected
veraxsystems
- network_management_system
CWE
CWE-798
Use of Hard-coded Credentials
