CVE-2015-2900
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 add_userfinding2 function in Medicomp MEDCIN Engine before 2.22.20153.226 allows remote attackers to cause a denial of service (out-of-bounds write) or possibly have unspecified other impact 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/add_userfinding2 function in Medicomp MEDCIN Engine versions prior to 2.22.20153.226 contains an out-of-bounds write vulnerability. Remote attackers can trigger this by sending a crafted packet to port 8190, causing denial of service or potentially achieving code execution via memory corruption.
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.20142.166CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Verify MEDCIN Engine is installedCheck for the presence of Medicomp MEDCIN Engine software on the system. Look for process names such as MEDCIN, MEDCINEngine, or check installed programs list for 'Medicomp MEDCIN Engine' or similar naming patterns.Affected if MEDCIN Engine software is found on the system
-
Determine the installed versionLocate the MEDCIN Engine executable or DLL file and query its version information. Common paths may include Program Files\Medicomp or application-specific directories. Right-click the executable, select Properties, and check the Version tab, or use command: dir /s *medcin*.exe or *medcin*.dll to find the binary, then check its version.Affected if Installed version is 2.22.20142.166 or lower
-
Check if port 8190 is listeningRun netstat -an | findstr :8190 or PowerShell Get-NetTCPConnection -LocalPort 8190 to determine if the MEDCIN Engine service is listening on the vulnerable port 8190.Affected if Port 8190 is in LISTENING state and accessible from network
-
Verify network exposure of port 8190Use nmap, netscan, or PowerShell Get-NetTCPConnection to confirm the binding address. Check if the port is bound to 0.0.0.0 or an external interface rather than localhost only. Review firewall rules for inbound access to port 8190.Affected if Port 8190 is exposed to untrusted network addresses
A system is affected if Medicomp MEDCIN Engine version 2.22.20142.166 or lower is installed AND port 8190 is accessible on the network.
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 MEDCIN Engine to version 2.22.20153.226 or later. As an interim control, restrict network access to port 8190 to trusted IPs only until the patch can be applied.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2900 — 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-2900 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