LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10238: bvlc.c in skarg BACnet Protocol Stack bacserv 0.9.1 and 0.8.5 is affected by a Buffer Overflow because of a...

bvlc.c in skarg BACnet Protocol Stack bacserv 0.9.1 and 0.8.5 is affected by a Buffer Overflow because of a lack of packet-size validation. The affected component is bacserv BACnet/IP BVLC forwarded NPDU. The function bvlc_bdt_forward_npdu() calls bvlc_encode_forwarded_npdu() which copies the content from the request into a local in the bvlc_bdt_forward_npdu() stack frame and clobbers the canary. The attack vector is: A BACnet/IP device with BBMD enabled based on this library connected to IP network. The fixed version is: 0.8.6.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-10238 is a packet-size validation flaw in the skarg BACnet Protocol Stack bacserv service. A BACnet/IP device using affected versions with BBMD enabled and reachable on an IP network could mishandle a forwarded NPDU packet and corrupt stack memory. Sources identify fixed version 0.8.6, but provide no CVSS severity or active exploitation evidence.

Executive priority

Prioritize environments where BACnet/IP crosses network boundaries or supports critical building operations. The issue is old and fixed, but embedded OT components can persist for years. Treat unknown vendor embedding as the main business risk until inventory confirms exposure.

Technical view

In bvlc.c, bvlc_bdt_forward_npdu() calls bvlc_encode_forwarded_npdu(), which copies request content into a local stack buffer without sufficient packet-size validation. The reported result is stack canary corruption in the BACnet/IP BVLC forwarded NPDU path. Affected versions named are bacserv 0.9.1 and 0.8.5; fixed version is 0.8.6.

Likely exposure

Exposure is most likely in building automation or OT environments running BACnet/IP devices based on the skarg stack, specifically bacserv 0.9.1 or 0.8.5 with BBMD enabled and IP network connectivity. The bundle does not identify downstream vendor products or CPEs.

Exploitation context

The source bundle describes a network attack vector against BACnet/IP devices with BBMD enabled. It does not cite public exploitation, CISA KEV listing, exploit availability, authentication requirements, or confirmed impact beyond stack memory corruption.

Researcher notes

The evidence is specific to bacserv's BVLC forwarded NPDU handling and BBMD-enabled BACnet/IP devices. Severity scoring, exploitability beyond canary corruption, and downstream product mapping are absent from the provided sources. Avoid extrapolating to all BACnet devices without confirming this library and affected versions.

Mitigation direction

  • Upgrade affected bacserv deployments to fixed version 0.8.6 where applicable.
  • Check vendor or integrator guidance for devices embedding the skarg BACnet stack.
  • Restrict BACnet/IP exposure to trusted management networks only.
  • Disable BBMD where it is not operationally required.
  • Inventory building automation devices for bacserv 0.9.1 and 0.8.5 usage.

Validation and detection

  • Identify BACnet/IP devices with BBMD enabled and IP network reachability.
  • Confirm whether devices or firmware use skarg bacserv 0.9.1 or 0.8.5.
  • Verify deployed stack version is 0.8.6 or later where applicable.
  • Review vendor advisories for embedded or rebranded BACnet implementations.
  • Confirm BACnet traffic is segmented from untrusted networks.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-10238 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.