# CVE-2010-3700: Authentication Bypass Using an Alternate Path or Channel in SpringSource Spring Security and Acegi Security

Source: https://junglewise.ai/threats/cve-2010-3700-authentication-bypass-using-an-alternate-path-or-channel-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2022-05-14  
License: CC BY 4.0 with a link back

CVE-2010-3700 · Severity: info · Published 2022-05-14

Authentication Bypass Using an Alternate Path or Channel in SpringSource Spring Security and Acegi Security

Technologies: [org.springframework.security:spring-security-core (Maven)](https://junglewise.ai/threats/technologies/org-springframework-security-spring-security-core). Vendors: [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

**Is CVE-2010-3700 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2010-3700 being exploited in the wild.

**How severe is CVE-2010-3700?** Informational severity, published 14 May 2022.

**Which products and versions are affected?** org.acegisecurity:acegi-security (Maven) ECOSYSTEM:introduced=1.0.0,last_affected=1.0.7; org.springframework.security:spring-security-core (Maven) ECOSYSTEM:introduced=2.0.0,fixed=2.0.6.

**Is there a fix for CVE-2010-3700?** Yes. org.springframework.security:spring-security-core (Maven): upgrade to 2.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2010-3700?** Check whether you run org.acegisecurity:acegi-security (Maven) or org.springframework.security:spring-security-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- org.springframework.security:spring-security-core (Maven): upgrade to 2.0.6 or later

  ```sh
  # set org.springframework.security:spring-security-core to 2.0.6 in your pom.xml or build.gradle
  ```


## Affected products

- org.acegisecurity:acegi-security (Maven) ECOSYSTEM:introduced=1.0.0,last_affected=1.0.7
- org.springframework.security:spring-security-core (Maven) ECOSYSTEM:introduced=2.0.0,fixed=2.0.6

## Identifiers

- CVE-2010-3700
- GHSA-3295-h9qx-r82x

## Related threats

- [Spring Security Vulnerable to User Attribute Enumeration when Using DaoAuthenticationProvider](https://junglewise.ai/threats/cve-2026-22746-spring-security-vulnerable-to-user-attribute-enumeration-when)
- [Spring Spring Security TOCTOU race condition in JdbcOneTimeTokenService](https://junglewise.ai/threats/cve-2026-22751-spring-spring-security-toctou-race-condition-in)
- [Spring Security has a broken timing attack mitigation implemented in DaoAuthenticationProvide](https://junglewise.ai/threats/cve-2025-22234-spring-security-has-a-broken-timing-attack-mitigation-implemented)
- [Spring Security annotation detection mechanism has authorization bypass](https://junglewise.ai/threats/cve-2025-41248-spring-security-annotation-detection-mechanism-has-authorization)
- [Spring Security authorization bypass for method security annotations on private methods](https://junglewise.ai/threats/cve-2025-41232-spring-security-authorization-bypass-for-method-security)