CVE-2010-1942 json
Unspecified vulnerability in the Servlet service in Fujitsu Limited Interstage Application Server 3.0 through 7.0, as used in Interstage Ap…
published 16y ago modified 4mo ago also EUVD-2010-1961
- cvss
- 6.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in the Servlet service in Fujitsu Limited Interstage Application Server 3.0 through 7.0, as used in Interstage Application Framework Suite, Interstage Business Application Server, and Interstage List Manager, allows attackers to obtain sensitive information or force invalid requests to be processed via unknown vectors related to unspecified invalid requests and settings on the load balancing device.
Patch / fix
Is CVE-2010-1942 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 FencerExploit prediction
1.56% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:P/A:N |
References
-
fujitsu.com
/global/support/software/security/products-f/interstage-201001e.html
patch, vendor-advisory
-
vupen.com
/english/advisories/2010/1165
vdb-entry, patch, vendor-advisory
-
software.fujitsu.com
/jp/security/vulnerabilities/jvn-90248889.html
vendor-advisory
-
secunia.com
/advisories/39803
third-party-advisory, vendor-advisory
-
jvndb.jvn.jp
/ja/contents/2010/JVNDB-2010-000018.html
third-party-advisory
-
osvdb.org
/64703
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/58634
vdb-entry
-
securityfocus.com
/bid/40189
vdb-entry
-
jvn.jp
/en/jp/JVN90248889/index.html
third-party-advisory
Sources
- CVE List CVE-2010-1942
- NVD CVE-2010-1942
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.