Improper Input Validation Affecting opendaylight package, versions *


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.19% (57th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-OPENDAYLIGHT-5248901
  • published1 Nov 2021
  • disclosed29 Jan 2018

Introduced: 29 Jan 2018

CVE-2018-1199  (opens in a new tab)
CWE-20  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:7 opendaylight.

NVD Description

Note: Versions mentioned in the description apply only to the upstream opendaylight package and not the opendaylight package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

Spring Security (Spring Security 4.1.x before 4.1.5, 4.2.x before 4.2.4, and 5.0.x before 5.0.1; and Spring Framework 4.3.x before 4.3.14 and 5.0.x before 5.0.3) does not consider URL path parameters when processing security constraints. By adding a URL path parameter with special encodings, 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. In this particular attack, different character encodings used in path parameters allows secured Spring MVC static resource URLs to be bypassed.

CVSS Scores

version 3.1