CVE-2013-10002
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was found in Telecommunication Software SAMwin Contact Center Suite 5.1. It has been rated as critical. Affected by this issue is the function getCurrentDBVersion in the library SAMwinLIBVB.dll of the credential handler. Authentication is possible with hard-coded credentials. Upgrading to version 6.2 is able to address this issue. It is recommended to upgrade the affected component.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHard-coded credentials vulnerability in the SAMwinLIBVB.dll library's credential handler (function getCurrentDBVersion) allows unauthorized authentication. This is a critical authentication bypass where static credentials are embedded in the software, enabling attackers to gain full access without legitimate user credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 5.01.19.06= 5.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate SAMwinLIBVB.dll on the systemSearch the filesystem for the file SAMwinLIBVB.dll. Typical locations may include the Samwin installation directory (for example, C:\Program Files\Telecomsoftware\Samwin or similar). Use commands like 'dir /s C:\SAMwinLIBVB.dll' on Windows or 'find / -name SAMwinLIBVB.dll' on Linux.Affected if The DLL file exists on the system, indicating the vulnerable library is present.
-
Confirm the Samwin product installationIdentify the installed Telecomsoftware Samwin product. Check for Samwin Agent version 5.01.19.06 or Samwin Contact Center version 5.1. Look in the software's About or Help menu, or check the Windows Programs and Features list (or equivalent package manager on other OSes).Affected if Samwin Agent version 5.01.19.06 or Samwin Contact Center version 5.1 is installed.
-
Verify the vulnerable function is accessibleThe vulnerability is in the getCurrentDBVersion function within SAMwinLIBVB.dll. This function handles credential processing. Check if the application connects to a database or uses the credential handler feature. Review application logs or network traffic for calls to this function.Affected if The application uses the getCurrentDBVersion function for database authentication.
-
Check for hardcoded credential exposureAnalyze the SAMwinLIBVB.dll binary or associated configuration files for static credentials. Use strings extraction tools on the DLL (for example, 'strings SAMwinLIBVB.dll') to search for embedded credentials or default credentials in plaintext.Affected if Hardcoded credentials are found embedded in the DLL or configuration.
You are affected if Telecomsoftware Samwin Agent version 5.01.19.06 or Samwin Contact Center version 5.1 is installed and the SAMwinLIBVB.dll library with the vulnerable getCurrentDBVersion function is present and active.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade SAMwin Contact Center Suite from version 5.1 to version 6.2 as specified in the vendor advisory. Prioritize this upgrade given the critical CVSS 9.1 severity and trivial exploitation via hardcoded credentials.
Samwin Contact Center Suite 6.2
- 1. Inventory all deployed instances of Samwin Agent version 5.01.19.06 and Samwin Contact Center version 5.1 in the environment
- 2. Create a complete backup of all configurations, databases, and user data for the affected Samwin installations
- 3. Obtain the Samwin Contact Center Suite version 6.2 upgrade package from the official vendor (www.samwin.com or authorized distributor)
- 4. Execute the upgrade to version 6.2 following the vendor's migration documentation
- 5. After upgrade, verify that the SAMwinLIBVB.dll library has been updated and no longer contains the vulnerable getCurrentDBVersion function with hard-coded credentials
- 6. Immediately change all system credentials, admin passwords, and database passwords that may have been exposed through the hard-coded credentials
- 7. Review and update any integration points (API keys, service accounts) that connect to the Samwin system
- 8. Validate that normal contact center operations resume correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-10002 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-10002 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data