CVE-2015-6006
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 · uneditedThe AddUserFinding implementation in Medicomp MEDCIN Engine 2.22.20153.x before 2.22.20153.226 might allow remote attackers to execute arbitrary code or cause a denial of service (integer truncation and heap-based buffer overflow) via a crafted packet on port 8190.
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 confidenceThe AddUserFinding function in Medicomp MEDCIN Engine versions prior to 2.22.20153.226 contains an integer truncation flaw that leads to a heap-based buffer overflow. Remote attackers can exploit this by sending crafted packets to port 8190, potentially achieving arbitrary code execution or causing denial of service.
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= 2.22.20153.223CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 Medicomp MEDCIN Engine installationSearch for medcin.dll, MEDCINEngine.exe, or similar MEDCIN-related files in common installation directories (e.g., C:\Program Files\Medicomp, C:\Program Files (x86)\Medicomp) or check Windows registry under HKLM\SOFTWARE\Medicomp for installation paths.Affected if The product is not found - not affected; if found, proceed to version check.
-
Determine installed MEDCIN Engine versionRight-click the MEDCIN executable or DLL file, select Properties, and check the Version tab. Alternatively, query the Windows registry under HKLM\SOFTWARE\Medicomp\MEDCIN\CurrentVersion if available.Affected if Version equals 2.22.20153.223 exactly - this is the affected version.
-
Compare version against affected rangeIf a version number is obtained, verify it matches 2.22.20153.223. Versions prior to 2.22.20153.223 or unknown versions should be treated as potentially vulnerable.Affected if Installed version is 2.22.20153.223.
-
Verify port 8190 is accessibleRun command: netstat -an | findstr :8190 to check if the service is listening. Also check firewall rules: netsh advfirewall firewall show rule name=all | findstr 8190.Affected if Port 8190 is listening and accessible from network - exposure risk exists.
-
Confirm AddUserFinding functionality is enabledReview application logs or configuration to determine if the AddUserFinding function is actively used or accessible. This is typically a clinical data entry feature in the MEDCIN Engine.Affected if AddUserFinding function is accessible to users or remote callers - exploitation path exists.
Environment is affected only if Medicomp MEDCIN Engine version 2.22.20153.223 is installed AND port 8190 is exposed and accessible to potential attackers.
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.
From vendor dataUpgrade Medicomp MEDCIN Engine to version 2.22.20153.226 or later. Consider network segmentation to restrict access to port 8190 until the patch is applied.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6006 — 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-2015-6006 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