dbcve.org
Cente Ipv6Application · Nxtech

CVE-2024-23911

HIGH · 7.5 CVSS v3.1 Published 2024-04-15
Fix available
A fix is available. Upgrade to after 2.30 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Out-of-bounds read vulnerability caused by improper checking of the option length values in IPv6 NDP packets exists in Cente middleware TCP/IP Network Series, which may allow an unauthenticated attacker to stop the device operations by sending a specially 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 confidence

Cente middleware TCP/IP Network Series contains an out-of-bounds read vulnerability in IPv6 NDP (Neighbor Discovery Protocol) packet processing. The middleware fails to properly validate option length values in incoming NDP packets, allowing an attacker to read memory beyond allocated buffers by sending specially crafted packets with manipulated option length fields.

MitigationApply vendor-provided patches for Cente TCP/IP Network Series middleware. If no patch available, consider network segmentation to restrict IPv6 NDP traffic or disable IPv6 if not required.

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
Cente Ipv6Application
Affected:<= 1.51
Cente Ipv6 Snmpv2Application
Affected:<= 2.30
Cente Ipv6 Snmpv3Application
Affected:<= 2.30

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cente middleware presence
    Locate the Cente TCP/IP Network Series middleware in your system or software bill of materials. Check product documentation or installed components for 'Cente Ipv6', 'Cente Ipv6 Snmpv2', or 'Cente Ipv6 Snmpv3'.
    Affected if The Cente TCP/IP Network Series middleware is present in your environment.
  2. Determine installed version
    Retrieve the version of the Cente middleware product in use. Compare against the affected version ranges: Nxtech Cente Ipv6 <= 1.51, Nxtech Cente Ipv6 Snmpv2 <= 2.30, Nxtech Cente Ipv6 Snmpv3 <= 2.30.
    Affected if The installed version falls within or below the affected version ranges.
  3. Verify IPv6 is enabled
    Check system or application configuration to determine if IPv6 networking functionality is enabled. This may be in network settings, middleware configuration, or runtime parameters.
    Affected if IPv6 is enabled and the system can process IPv6 traffic.
  4. Confirm NDP packet processing is active
    Determine whether the system processes IPv6 NDP (Neighbor Discovery Protocol) packets. NDP is required for the vulnerability to be triggerable.
    Affected if The system accepts and processes incoming IPv6 NDP packets.

You are affected if Cente TCP/IP Network Series middleware is present with a version at or below the affected ranges AND IPv6 with NDP packet processing is enabled in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 2.30
Interim mitigation

Apply vendor-provided patches for Cente TCP/IP Network Series middleware. If no patch available, consider network segmentation to restrict IPv6 NDP traffic or disable IPv6 if not required.

Recommended fix Moderate confidence

Cente Ipv6: 1.52+ | Cente Ipv6 Snmpv2: 2.31+ | Cente Ipv6 Snmpv3: 2.31+

  1. Contact Cente (www.cente.jp) to obtain the fixed version of Cente Ipv6 (version 1.52 or later)
  2. Contact Cente to obtain the fixed version of Cente Ipv6 Snmpv2 (version 2.31 or later)
  3. Contact Cente to obtain the fixed version of Cente Ipv6 Snmpv3 (version 2.31 or later)
  4. Upgrade all affected installations to the fixed versions provided by the vendor
  5. Test the upgrade in a non-production environment before deploying to production
Caveat Review Cente release notes for any compatibility changes or migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cente Ipv6 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23911 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23911 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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