CVE-2015-2901
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 · uneditedMultiple stack-based buffer overflows in Medicomp MEDCIN Engine 2.22.20142.166 might allow remote attackers to execute arbitrary code via a crafted packet on port 8190, related to (1) the GetProperty info_getproperty function and (2) the GetProperty UdfCodeList function.
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 · moderate confidenceStack-based buffer overflow in Medicomp MEDCIN Engine allows remote code execution via crafted packets on port 8190. Two functions are affected: GetProperty info_getproperty and GetProperty UdfCodeList. Attackers can overflow stack buffers by sending specially crafted data, potentially achieving arbitrary code execution.
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.
-
Identify Medicomp MEDCIN Engine installation and versionLocate the MEDCIN Engine installation directory and check the version information (typically found in the application executable, DLL properties, or version file). Compare your installed version against the affected version 2.22.20142.166.Affected if The installed version matches 2.22.20142.166 exactly.
-
Verify port 8190 is listeningUse netstat or equivalent network utility to check if port 8190 is in LISTEN state on any network interface (e.g., 'netstat -an | grep 8190' or 'Get-NetTCPConnection -LocalPort 8190' on Windows).Affected if Port 8190 is open and listening on the system.
-
Confirm MEDCIN Engine service is runningCheck if the Medicomp MEDCIN Engine service or process is actively running on the system.Affected if The MEDCIN Engine service is running and port 8190 is exposed.
-
Assess network exposure of port 8190Review firewall rules, network configuration, or binding addresses to determine if port 8190 is accessible from network segments beyond localhost.Affected if Port 8190 is accessible from network hosts rather than localhost-only.
A system is affected if it runs Medicomp MEDCIN Engine version 2.22.20142.166 with port 8190 open and 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 dataRestrict network access to port 8190; apply vendor patch when available; if patch unavailable, implement input validation and bounds checking on the affected GetProperty functions.
- Consultation4.0 h
- Implementation12.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2901 — 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-2901 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