dbcve.org
Cente Ipv6Application · Nxtech

CVE-2024-28894

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-15
Fix available
A fix is available. Upgrade to after 2.30 or later.
See remediation →
62/100
Remediation priority · Elevated
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 headers 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 TCP/IP Network Series middleware contains an out-of-bounds read vulnerability in IPv6 header processing due to insufficient validation of option length values. An unauthenticated attacker can send a specially crafted IPv6 packet with malformed options to trigger the vulnerability, causing denial of service by stopping device operations.

MitigationApply the vendor's patch or update to the Cente TCP/IP Network Series middleware that addresses the IPv6 option length validation. If no patch is available, consider network segmentation to limit exposure to untrusted IPv6 traffic.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 the installed Cente middleware version
    Locate and read the version information for Nxtech Cente Ipv6, Cente Ipv6 Snmpv2, or Cente Ipv6 Snmpv3 in your system documentation, installed software inventory, or by querying the middleware directly if a version API is available
    Affected if The installed version is 1.51 or lower for Ipv6, or 2.30 or lower for Snmpv2/Snmpv3
  2. Confirm IPv6 functionality is enabled
    Check the product configuration or runtime settings to determine whether IPv6 protocol processing is active in your deployment
    Affected if IPv6 processing is enabled and the vulnerable code path can be exercised
  3. Verify network exposure to IPv6 traffic
    Inspect network interfaces and firewall rules to determine if the system can receive IPv6 packets from untrusted sources
    Affected if The system accepts IPv6 packets from network segments or interfaces that are accessible to unauthenticated attackers

A system is affected if it runs any of the listed Cente products at vulnerable versions with IPv6 enabled and accessible to untrusted IPv6 traffic.

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 the vendor's patch or update to the Cente TCP/IP Network Series middleware that addresses the IPv6 option length validation. If no patch is available, consider network segmentation to limit exposure to untrusted IPv6 traffic.

Recommended fix Moderate confidence

Cente Ipv6: version 1.52 or later | Cente Ipv6 Snmpv2: version 2.31 or later | Cente Ipv6 Snmpv3: version 2.31 or later

  1. 1. Identify the specific Cente product variant in use (Cente Ipv6, Cente Ipv6 Snmpv2, or Cente Ipv6 Snmpv3)
  2. 2. Contact Cente technical support or visit www.cente.jp to obtain the latest fixed version
  3. 3. Ensure backup of current configuration before performing upgrade
  4. 4. Apply the upgrade to a version higher than the vulnerable release (greater than 1.51 for Cente Ipv6, greater than 2.30 for Snmpv2/Snmpv3)
  5. 5. Verify the upgrade was successful and test normal device operations
Caveat Review vendor release notes for any configuration or compatibility changes in the new version

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-28894 — 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-28894 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