p PatchFirst

CVE-2018-1199

CVE-2018-1199

CVSS 5.3 · Medium · EPSS 2.8% · Fix available

Compare with your installed version

Affected products and known fixed versions are public information. Compare them with your installed version.

Check the installed version:

dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="libspring-java"'

Assess your server’s risks

The free check gives you a rating and a risk summary by technology stack, without signing up. It does not answer whether this particular vulnerability affects you.

Monitoring matches public information against your servers’ software. Detailed findings for your servers include the order of updates.

curl -fsSL https://patchfirst.dev/check.sh | sh
Check your server for free →

Channels carry general technology news; monitoring reports new findings on your servers in your dashboard, through browser notifications, in Telegram or via a webhook.

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

Published
Updated

Stack: system

Affected products and versions

  • spring by pivotal

    Versions
    • spring Security 4.1.0 - 4.1.4, 4.2.0 - 4.2.3, 5.0.0: Affected
    • Spring Framework 5.0.0 - 5.0.2, 4.3.0 - 4.3.13: Affected
    • Older unmaintained versions of Spring Security & Spring Framework were not analyzed and may be impacted: Affected

    No fix published

  • libspring-java Debian 12

    Affected ranges
    • ECOSYSTEM: < 4.3.14-1

    Update to 4.3.14-1

  • libspring-java Debian 13

    Affected ranges
    • ECOSYSTEM: < 4.3.14-1

    Update to 4.3.14-1

  • libspring-java Debian 14

    Affected ranges
    • ECOSYSTEM: < 4.3.14-1

    Update to 4.3.14-1

  • libspring-java Ubuntu Pro 14.04 LTS

    Versions
    • 3.0.6.RELEASE-7
    • 3.0.6.RELEASE-8
    • 3.0.6.RELEASE-9
    • 3.0.6.RELEASE-10
    • 3.0.6.RELEASE-11
    • 3.0.6.RELEASE-12
    All versions (9)
    • 3.0.6.RELEASE-13
    • 3.0.6.RELEASE-13ubuntu0.1~esm1
    • 3.0.6.RELEASE-13ubuntu0.1~esm2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • libspring-java Ubuntu Pro 16.04 LTS

    Versions
    • 3.2.13-3
    • 3.2.13-4
    • 3.2.13-5
    • 3.2.13-5ubuntu0.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →