Vulnerability in libspring-java
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as DEBIAN-CVE-2018-1199 has been found in libspring-java.
Risk of unauthorized operations or information disclosure.
What to do: upgrade libspring-java to 4.3.14-1 or later.
If unsure, ask your IT team or search "libspring-java DEBIAN-CVE-2018-1199" on the vendor's site.
DEBIAN-CVE-2018-1199 (libspring-java)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.3.14-1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in libspring-java.
Check the vendor advisory for the affected versions of libspring-java.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.3.14-1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'libspring-java' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'libspring-java' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
libspring-javaを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade libspring-java to 4.3.14-1ステージング環境で 4.3.14-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Debian:12 | libspring-java |
< 4.3.14-1 |
4.3.14-1 |
| Debian:13 | libspring-java |
< 4.3.14-1 |
4.3.14-1 |
| Debian:14 | libspring-java |
< 4.3.14-1 |
4.3.14-1 |
Original description The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory security-tracker.debian.org