- Assigned byThe organization (CNA) that assigned this CVE ID and published the record, usually the vendor.
- Dell (opens in new tab)
- Published
- Last modified
- NVD statusWhether NVD has reviewed the record. Until it has, scores and product data come from the reporting organization alone. About NVD's statuses
- Modified
Description
An issue was discovered in Pivotal Spring Security before 3.2.10, 4.1.x before 4.1.4, and 4.2.x before 4.2.1. Spring Security does not consider URL path parameters when processing security constraints. By adding a URL path parameter with an encoded "/" to a request, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification. Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. The unexpected presence of path parameters can cause a constraint to be bypassed. Users of Apache Tomcat (all current versions) are not affected by this vulnerability since Tomcat follows the guidance previously provided by the Servlet Expert group and strips path parameters from the value returned by getContextPath(), getServletPath(), and getPathInfo(). Users of other Servlet containers based on Apache Tomcat may or may not be affected depending on whether or not the handling of path parameters has been modified. Users of IBM WebSphere Application Server 8.5.x are known to be affected. Users of other containers that implement the Servlet specification may be affected.
Exploitation
Whether attackers are exploiting this vulnerability, and how likely they are to try in the next 30 days.
FIRST Exploit Prediction Scoring System (EPSS)About EPSS (opens in new tab)
FIRST's estimate of the chance attackers try to exploit this vulnerability in the next 30 days.
- Probability of exploitationIt predicts attempts, not success, and is updated daily.
- 1.455%
- Compared with other CVEs
- At or above 74.115% of scored CVEs
- Scored
Affected products
The products and versions with the vulnerability.
Listed by CNA
The products and versions affected, according to the organization that published this CVE.
| Vendor | Product | Affected versions |
|---|---|---|
| Pivotal Spring Security before 3.2.10, 4.1.x before 4.1.4, and 4.2.x before 4.2.1 |
|
Listed by NVD
The CPE names vulnerability scanners match, including products that bundle the affected software.
| Vendor | Product | Type | Vulnerable versions |
|---|---|---|---|
| ibm | websphere application server | Application |
|
| vmware | spring security | Application |
|
Recommended actions
How to fix the vulnerability, or reduce the risk until you can.
Patches, advisories and mitigations
Tagged by NVD.
- Vendor Advisory
- Mailing List
Severity
How serious the vulnerability is if exploited, scored from 0 to 10 with the CVSS standard (opens in new tab).
- 7.5 HighCVSS 3.0 · PrimaryPrimary scores are NVD's own. Secondary scores come from the organization that published the CVE, or from CISA. · Scored by NVD (opens in new tab)
- Attack vectorWhere the attacker has to be. Network is the widest: anywhere on the Internet.
- Network
- Attack complexityWhether the attack depends on conditions the attacker doesn't control.
- Low
- Privileges requiredThe access the attacker needs before attacking.
- None
- User interactionWhether someone other than the attacker has to do something, like open a link.
- None
- ScopeWhether the attack can reach beyond the vulnerable component.
- Unchanged
- ConfidentialityHow much data the attacker can read.
- None
- IntegrityHow much data the attacker can change.
- High
- AvailabilityHow much the attacker can disrupt the system or service.
- None
CVSS:3.0/View in FIRST's calculator (opens in new tab)AV:N/ AC:L/ PR:N/ UI:N/ S:U/ C:N/ I:H/ A:N - 5 MediumCVSS 2.0 · PrimaryPrimary scores are NVD's own. Secondary scores come from the organization that published the CVE, or from CISA. · Scored by NVD (opens in new tab)
- Attack vectorWhere the attacker has to be. Network is the widest: anywhere on the Internet.
- Network
- Attack complexityWhether the attack depends on conditions the attacker doesn't control.
- Low
- AuthenticationHow many times the attacker has to sign in.
- None
- ConfidentialityHow much data the attacker can read.
- None
- IntegrityHow much data the attacker can change.
- Partial
- AvailabilityHow much the attacker can disrupt the system or service.
- None
AV:N/View in NVD's calculator (opens in new tab)AC:L/ Au:N/ C:N/ I:P/ A:N
Weaknesses and attack patterns
The type of bug behind the vulnerability, and how attackers exploit that type.
Communication Channel Errors · CWE-417 (opens in new tab)
Weaknesses in this category are related to improper handling of communication channels and access paths. These weaknesses include problems in creating, managing, or removing alternate channels and alternate paths. Some of these can overlap virtual file problems and are commonly used in "bypass" attacks, such as those that exploit authentication errors.
- Mapping guidanceWhether MITRE recommends citing this weakness type for a single vulnerability. Broad types are discouraged in favor of more specific ones. About MITRE's mapping guidance
- Prohibited
References
Advisories, patches, exploits and more about this vulnerability.
This product uses the NVD API but is not endorsed or certified by the NVD (opens in new tab). CVE records from the CVE List (opens in new tab), weakness types from MITRE's CWE (opens in new tab)™ and attack patterns from its CAPEC (opens in new tab)™ are © The MITRE Corporation, used under the CVE (opens in new tab), CWE (opens in new tab) and CAPEC (opens in new tab) terms of use. Known exploited vulnerabilities and SSVC assessments are from CISA. Exploit predictions are from FIRST's EPSS (opens in new tab). About this data