CVE-2015-0979
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 · uneditedHeap-based buffer overflow in the SOAP web interface in SCADA Engine BACnet OPC Server before 2.1.371.24 allows remote attackers to execute arbitrary code via a crafted packet.
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 confidenceHeap-based buffer overflow vulnerability in the SOAP web interface of SCADA Engine BACnet OPC Server prior to version 2.1.371.24. The flaw allows remote attackers to execute arbitrary code via crafted SOAP packets, exploiting heap 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.1.359.22CVSS 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
- Complete
AV:N/AC:L/Au:N/C:P/I:P/A:C
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 BACnet OPC Server is installedCheck for the SCADA Engine BACnet OPC Server service or executable on the system. Look for process named 'BACnetOPCServer' or check Program Files for the installation directory.Affected if The software is present on the system
-
Identify installed versionLocate the BACnet OPC Server executable and check its version property, or check the installed software version in Windows Add/Remove Programs or the application's About/Info dialog.Affected if The version is 2.1.359.22 or lower (any version <= 2.1.359.22)
-
Confirm SOAP web interface is enabledExamine the BACnet OPC Server configuration files or settings for SOAP web service/enableSOAP or similar web interface settings. Check if a web service port (typically 80/443 or configured HTTP port) is listening.Affected if The SOAP web interface is active and accepting connections
-
Assess network exposureReview network bindings and firewall rules to determine if the SOAP port is exposed to network interfaces beyond localhost. Use 'netstat -an' or similar to identify listening ports associated with the application.Affected if The SOAP service is reachable from untrusted network segments
If BACnet OPC Server version 2.1.359.22 or lower is installed with the SOAP web interface enabled and accessible, the environment is affected by this vulnerability.
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 to BACnet OPC Server version 2.1.371.24 or later. Apply network segmentation to isolate SCADA systems from untrusted networks, and implement intrusion detection to monitor for anomalous SOAP traffic.
2.1.371.24
- 1. Identify the current version of SCADA Engine BACnet OPC Server installed on the system
- 2. Download version 2.1.371.24 or later from the official SCADA Engine vendor or authorized distributor
- 3. Create a full backup of the current system configuration and data
- 4. Stop the BACnet OPC Server service before applying the update
- 5. Install version 2.1.371.24 or later of the BACnet OPC Server
- 6. Verify the installation was successful by checking the version number
- 7. Restart the BACnet OPC Server service
- 8. Test critical BACnet functionality to ensure normal operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0979 — 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-0979 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