Menu

Star on GitHub · 3.2k

CVE-2010-0616

7.5 · HIGH

evalSMSI 2.1.03 stores passwords in cleartext in the database, which allows attackers with database access to gain privileges.

Published Feb 11, 2010myshellCWE-255EPSS 1.17%

Overview

CVE-2010-0616 is a high-severity vulnerability affecting myshell evalsmsi. It was published on February 11, 2010 and has a CVSS 2.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

evalSMSI 2.1.03 stores passwords in cleartext in the database, which allows attackers with database access to gain privileges. NOTE: remote attack vectors are possible by leveraging a separate SQL injection vulnerability.

Remediation

Check the references section for vendor advisories and patches from myshell. Update evalsmsi to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2010-0616?

CVE-2010-0616 is a high-severity vulnerability affecting myshell evalsmsi. It was published on February 11, 2010 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2010-0616?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2010-0616?

Check the references section for vendor advisories and patches from myshell. Update evalsmsi to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2010-0616?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2010-0616 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2010

View all