CVE-2025-3791
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 vulnerability classified as critical was found in symisc UnQLite up to 957c377cb691a4f617db9aba5cc46d90425071e2. This vulnerability affects the function jx9MemObjStore of the file /data/src/benchmarks/unqlite/unqlite.c. The manipulation leads to heap-based buffer overflow. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.
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 confidenceHeap-based buffer overflow in the jx9MemObjStore function of UnQLite database library allows local attackers to overwrite heap memory by manipulating memory object storage operations. The vulnerability exists in the bounds checking logic when storing memory objects.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate UnQLite library or binarySearch for files named 'unqlite', 'libunqlite', or binaries that link against UnQLite using commands like 'find / -name "*unqlite*" 2>/dev/null' or 'ldconfig -p | grep -i unqlite'Affected if UnQLite library or any application using it is found on the system
-
Identify the jx9MemObjStore functionUse 'nm libunqlite.so' or 'objdump -T libunqlite.so | grep jx9MemObjStore' to check if the vulnerable function exists in the installed libraryAffected if The jx9MemObjStore function symbol is present in the UnQLite library
-
Check for UnQLite version informationRun 'unqlite -version' if available, or check library file metadata with 'file libunqlite.so', or examine any embedded version strings with 'strings libunqlite.so | grep -i version'Affected if No version information is available or the version predates the fix (the vendor uses continuous delivery with no fixed version numbers, making exact comparison difficult)
-
Inspect applications using UnQLiteIdentify any applications that bundle or link to UnQLite using 'ldd <application>' or by checking application dependenciesAffected if Any application that embeds or links to an unpatched version of UnQLite is in use
The environment is affected if UnQLite library or any application using it is present and the jx9MemObjStore function exists without an available patch or updated commit from the vendor.
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 dataSince UnQLite uses continuous delivery with no fixed versions, obtain and integrate the latest commit or patch from the vendor. Implement proper boundary validation in jx9MemObjStore before memory operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3791 — 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-2025-3791 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