CVE-2010-3700 json
Authentication Bypass Using an Alternate Path or Channel in SpringSource Spring Security and Acegi Security
published 16y ago modified 4mo ago also GHSA-3295-h9qx-r82x , EUVD-2022-2081
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
VMware SpringSource Spring Security 2.x before 2.0.6 and 3.x before 3.0.4, and Acegi Security 1.0.0 through 1.0.7, as used in IBM WebSphere Application Server (WAS) 6.1 and 7.0, allows remote attackers to bypass security constraints via a path parameter.
Patch / fix
- maven org.springframework.security:spring-security-core 2.0.6, 3.0.4
Is CVE-2010-3700 in your dependencies? 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.69% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.security:spring-security-core | >=2.0.0, <2.0.6 >=3.0.0, <3.0.4 |
2.0.6 3.0.4 |
| maven | org.acegisecurity:acegi-security | >=1.0.0, <=1.0.7 |
no fix listed |
Classification
- Weakness
- Technology feeds
References
-
securityfocus.com
/bid/44496
vdb-entry
-
secunia.com
/advisories/42024
third-party-advisory
-
issues.apache.org
/bugzilla/show_bug.cgi?id=25015
web
- springsource.com /security/cve-2010-3700
-
osvdb.org
/68931
vdb-entry
-
securityfocus.com
/archive/1/514517/100/0/threaded
mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2010-3700
advisory
-
web.archive.org
/web/20110802082343/http://www.springsource.com/security/cve-2010-3700
web
Sources
- CVE List CVE-2010-3700
- GitHub Advisory GHSA-3295-h9qx-r82x
- NVD CVE-2010-3700
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.