high
7.5
CWE
20
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2018-1199: Input Validation

First published: Mon Jan 29 2018(Updated: )

Pivotal Spring Security and Spring Framework could allow a remote attacker to bypass security restrictions, caused by the failure to consider URL path parameters when processing security constraints. By adding a URL path parameter with special encodings, an attacker could exploit this vulnerability to bypass access restrictions and gain access to the server and obtain sensitive information.

Credit: security_alert@emc.com security_alert@emc.com

Affected SoftwareAffected VersionHow to fix
IBM GDE<=3.0.0.2
VMware Spring Framework>=4.3.0<4.3.14
VMware Spring Framework>=5.0.0<5.0.3
Vmware Spring Security>=4.1.0<4.1.5
Vmware Spring Security>=4.2.0<4.2.4
Vmware Spring Security>=5.0.0<5.0.1
Redhat Fuse=1.0
Oracle Rapid Planning=12.1
Oracle Rapid Planning=12.2
Oracle Retail Xstore Point of Service=7.1
redhat/springframework<5.0.3
5.0.3
redhat/springframework<4.3.14
4.3.14
redhat/springframework-security<5.0.1
5.0.1
redhat/springframework-security<4.2.4
4.2.4
redhat/springframework-security<4.1.5
4.1.5
maven/org.springframework.security:spring-security-core>=5.0.0<5.0.1
5.0.1
maven/org.springframework.security:spring-security-core>=4.2.0<4.2.4
4.2.4
maven/org.springframework.security:spring-security-core>=4.1.0<4.1.5
4.1.5
maven/org.springframework:spring-core>=5.0.0<5.0.3
5.0.3
maven/org.springframework:spring-core>=4.3.0<4.3.14
4.3.14

Remedy

As a general precaution, users are encouraged to separate public and private resources. For example, separating static resources and mapping them to /resources/public/** and /resources/private/** is preferred to having one common root with mixed public and private resource content underneath.

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the vulnerability ID for this security issue?

    The vulnerability ID for this security issue is CVE-2018-1199.

  • What is the severity of CVE-2018-1199?

    The severity of CVE-2018-1199 is high, with a severity value of 7.5.

  • Which software is affected by CVE-2018-1199?

    The software affected by CVE-2018-1199 includes Pivotal Spring Security (versions before 4.1.5, 4.2.4, and 5.0.1) and Spring Framework (versions before 4.3.14 and 5.0.3).

  • How can a remote attacker exploit CVE-2018-1199?

    A remote attacker can exploit CVE-2018-1199 by bypassing security restrictions and adding a URL path parameter with special encodings.

  • Are there any references for more information about CVE-2018-1199?

    Yes, you can find more information about CVE-2018-1199 at the following references: [link1](https://pivotal.io/security/cve-2018-1199), [link2](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1540033), [link3](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1540032).

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203