CVE-2023-35661
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 · uneditedIn ProfSixDecomTcpSACKoption of RohcPacketCommon.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
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 · high confidenceAn out-of-bounds read vulnerability exists in the ROHC (Robust Header Compression) library's TCP SACK (Selective Acknowledgment) option decompression function (ProfSixDecomTcpSACKoption). The function fails to validate buffer bounds before reading data, allowing an attacker to read adjacent memory contents and disclose sensitive information without requiring user interaction or elevated privileges.
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 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 the ROHC library on the Android deviceSearch for librouhc.so in system directories (e.g., /system/lib/, /vendor/lib/, or via 'find / -name librouhc.so 2>/dev/null')Affected if The ROHC library file exists on the device, meaning the vulnerable code is present
-
Identify processes using the ROHC libraryRun 'adb shell dumpsys meminfo | grep -i rohc' or use 'adb shell pidof <app>' combined with 'adb shell cat /proc/<pid>/maps' to see if any running process has loaded librouhc.soAffected if Any application or system service has loaded the ROHC library into memory, enabling the attack surface
-
Check for network components that handle ROHC-compressed trafficInspect installed apps for components that process IP header compression (look for packages using android.net or telephony services that may handle ROHC, or check logcat for ROHC-related messages during network activity)Affected if Applications or system services that process ROHC-compressed network packets are in use, triggering the vulnerable decompression code path
-
Verify Android framework ROHC supportCheck /system/etc/permissions/platform.xml or framework JARs for ROHC-related permissions and classes (search for 'rohc' in /system/framework/ or via 'adb shell pm list features | grep -i rohc')Affected if Android features or permissions related to ROHC decompression are enabled on the device
The device is affected if the ROHC library exists and any component uses it to decompress TCP SACK options, since the vulnerability affects all Android versions with ROHC support.
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 dataApply the vendor patch or update the ROHC library to a version containing proper bounds validation in the TCP SACK decompression routine. If no patch is available, consider disabling ROHC decompression or implementing input validation at the network perimeter.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35661 — 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-35661 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