CVE-2010-3894 in the critical feed json
Stack-based buffer overflow in the Java_com_ibm_es_oss_CryptionNative_ESEncrypt function in /opt/IBM/es/lib/libffq.cryptionjni.so in the lo…
published 15y ago modified 4mo ago also EUVD-2010-3872
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 12.0%
- EPSS 12.0% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
Stack-based buffer overflow in the Java_com_ibm_es_oss_CryptionNative_ESEncrypt function in /opt/IBM/es/lib/libffq.cryptionjni.so in the login form in the administration interface in IBM OmniFind Enterprise Edition before 8.5 FP6 allows remote attackers to execute arbitrary code via a long password.
Is CVE-2010-3894 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-15474)
- Published
Exploit prediction
12.02% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15474 IBM OmniFind - Buffer Overflow dos, 2010-11-09
- security.fatihkilic.de http://security.fatihkilic.de/advisory/fkilic-sa-2010-ibm-omnifind.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
exploit-db.com
/exploits/15474
exploit
-
security.fatihkilic.de
/advisory/fkilic-sa-2010-ibm-omnifind.txt
exploit
-
securityfocus.com
/archive/1/514688/100/0/threaded
mailing-list
-
securityfocus.com
/bid/44740
vdb-entry
-
vupen.com
/english/advisories/2010/2933
vdb-entry
-
osvdb.org
/69079
vdb-entry
Sources
- CVE List CVE-2010-3894
- NVD CVE-2010-3894
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.