CVE-2023-5685
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 · uneditedA flaw was found in XNIO. The XNIO NotifierState that can cause a Stack Overflow Exception when the chain of notifier states becomes problematically large can lead to uncontrolled resource management and a possible denial of service (DoS).
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 confidenceXNIO's NotifierState implementation contains a flaw where excessively large chains of notifier states can trigger a Stack Overflow Exception. This occurs due to uncontrolled recursion or chaining of notifier states without proper limits, leading to uncontrolled resource management and potential denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Locate XNIO library filesSearch for XNIO JAR files or Maven/Gradle dependencies in your project. Common file patterns: xnio-api-*.jar, xnio-nio-*.jar, or dependency declarations containing 'org.xnio:xnio-api' or 'org.xnio:xnio-nio'Affected if XNIO library is present in the environment
-
Determine installed XNIO versionInspect the JAR file name for version number, or check build manifest/pom.xml/gradle.lock file for the xnio-api or xnio-nio artifact version. Compare against any known patched versions if availableAffected if The installed version is older than the patched version that fixes the NotifierState chain length issue
-
Verify NotifierState implementation is in useSearch application code for usage of NotifierState, Notifier, or notifier-related classes from XNIO package. Check if the application uses XNIO for I/O operations that involve notification callbacks or state machinesAffected if The application uses XNIO's NotifierState or related notifier functionality that could create chained states
-
Check for notifier chain configurationExamine application configuration files, XML descriptors, or properties files for any settings related to notifier depth, chain limits, or stack size. Look for keys containing 'notifier', 'chain', 'depth', or 'stack' in configuration directoriesAffected if No limits are configured on notifier chain depth or stack usage
-
Monitor for Stack Overflow related to XNIOReview application logs for StackOverflowError exceptions, especially those reference XNIO classes or notifier operations. Check if the application experiences intermittent crashes or thread termination related to stack exhaustionAffected if Stack Overflow errors are occurring in XNIO notifier operations
A user is affected if XNIO with a vulnerable NotifierState implementation is present and the application uses notifier functionality that can create chained states without depth limits.
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 dataUpdate XNIO to the latest patched version that addresses the NotifierState chain length issue. If no patch is available, implement application-level controls to limit notifier chain depth and monitor for abnormal stack usage patterns.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5685 — 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-5685 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