CVE-2023-49713
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 · uneditedDenial-of-service (DoS) vulnerability exists in NetBIOS service of HMI GC-A2 series. If a remote unauthenticated attacker sends a specially crafted packets to specific ports, a denial-of-service (DoS) condition may occur.
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 confidenceA denial-of-service vulnerability exists in the NetBIOS service of HMI GC-A2 series devices. A remote unauthenticated attacker can send specially crafted packets to specific ports on the affected device, causing the NetBIOS service to fail and resulting in a DoS condition.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 the HMI device modelLocate the device label, documentation, or web interface to confirm the exact model number (e.g., GC-A22w, GC-A24w, GC-A26w, GC-A24, GC-A24M, GC-A25, GC-A26, or GC-A26J2)Affected if The device is any of the listed Jtekt GC-A2 series models (A22w, A24w, A26w, A24, A24M, A25, A26, or A26J2)
-
Verify NetBIOS service statusAccess the device management interface or check system services to determine if the NetBIOS Name Service, NetBIOS Datagram Service, or NetBIOS Session Service is enabledAffected if NetBIOS services are enabled on the device (UDP ports 137, 138, or 139 are active)
-
Scan for open NetBIOS portsUse a network scanner (such as nmap) to probe UDP ports 137, 138, and 139 on the device IP address: nmap -sU -p 137-139 <device_ip>Affected if Any of UDP ports 137, 138, or 139 are open and responding on the target device
-
Assess network accessibility of NetBIOS portsDetermine if the device NetBIOS ports are reachable from untrusted network segments by reviewing firewall rules, ACLs, or by performing an external port scan from an untrusted hostAffected if UDP ports 137-139 are accessible from network segments outside the trusted management or operational zone
The environment is affected if a Jtekt GC-A2 series HMI device has NetBIOS services enabled and UDP ports 137-139 are accessible to untrusted 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 dataRestrict network access to the affected HMI device's NetBIOS ports (typically UDP 137-139) via firewall rules or network segmentation. If NetBIOS is not required for operational purposes, disable the service.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49713 — 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-2023-49713 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