dbcve.org
Springsource Spring SecurityFramework / library · VMware

CVE-2010-3700

MEDIUM · 5.0 CVSS v2.0 Published 2010-10-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 · moderate confidence

VMware SpringSource Spring Security 2.x before 2.0.6 and 3.x before 3.0.4, and Acegi Security 1.0.0-1.0.7, as used in IBM WebSphere Application Server 6.1 and 7.0, allows remote attackers to bypass security constraints via a path parameter in the URL.

MitigationUpgrade Spring Security to version 2.0.6 or 3.0.4 or later; alternatively apply IBM WebSphere security patches or implement URL parameter validation at the web application firewall or application layer.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Springsource Spring SecurityFramework / library
Affected:= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 3.0.0= 3.0.1= 3.0.2= 3.0.3
Acegi SecurityApplication
Affected:= 1.0.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7
Websphere Application ServerApplication
Affected:= 6.1= 7.0

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
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring Security or Acegi Security version in use
    Locate the spring-security-core.jar or acegi-security jar in the application's WEB-INF/lib directory or WebSphere shared library path. Open the MANIFEST.MF file inside the jar and look for the Implementation-Version attribute.
    Affected if The version reads 2.0.0 through 2.0.5, 3.0.0 through 3.0.3, or any 1.0.0 through 1.0.7 version of Acegi Security
  2. Confirm WebSphere Application Server version
    From the WebSphere Administrative Console, navigate to Servers > Server Types > WebSphere Application Servers, select your server, and view the version information. Alternatively, check the install_root/properties/version.txt file.
    Affected if The server version is listed as 6.1 or 7.0
  3. Verify Spring Security filter is configured in the application
    Examine the application's WEB-INF/web.xml file for a filter definition named 'springSecurityFilterChain' or 'Acegi Security Filter' and its corresponding filter-mapping URL patterns.
    Affected if A Spring Security or Acegi Security filter is mapped to URL patterns and is actively protecting resources
  4. Check if URL parameter handling is the security mechanism
    Review the spring-security.xml or applicationContext-security.xml configuration files to confirm that filter security is applied to URL paths (such as intercept-url patterns with access='ROLE_USER' or similar).
    Affected if URL-based access control rules are defined and enforced by Spring Security or Acegi Security

You are affected if your application uses Spring Security 2.0.0-2.0.5, 3.0.0-3.0.3, or Acegi Security 1.0.0-1.0.7, deployed on WebSphere Application Server 6.1 or 7.0, with Spring Security filters protecting URL paths.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Spring Security to version 2.0.6 or 3.0.4 or later; alternatively apply IBM WebSphere security patches or implement URL parameter validation at the web application firewall or application layer.

Fix this in Springsource Spring Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-3700 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-3700 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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