Vulnerability in ocsinventory-server (DEBIAN-CVE-2018-1000558)
Summary
Vulnerability in ocsinventory-server (DEBIAN-CVE-2018-1000558). Confidential information can be exposed externally. Mitigation: upgrade to 2.4.1 or later.
Original description
The description as published by the source.
OCS Inventory NG ocsreports 2.4 and ocsreports 2.3.1 version 2.4 and 2.3.1 contains a SQL Injection vulnerability in web search that can result in An authenticated attacker is able to gain full access to data stored within database. This attack appear to be exploitable via By sending crafted requests it is possible to gain database access. This vulnerability appears to have been fixed in 2.4.1.
Source: OSV.dev (Open Source Vulnerabilities) OSV
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-1000558 has been found in ocsinventory-server.
Confidential information can be exposed externally.
What to do: upgrade ocsinventory-server to 2.4.1 or later.
If unsure, ask your IT team or search "ocsinventory-server DEBIAN-CVE-2018-1000558" on the vendor's site.
DEBIAN-CVE-2018-1000558 (ocsinventory-server)
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.4.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 ocsinventory-server.
Check the vendor advisory for the affected versions of ocsinventory-server.
Severity: ?. Confidential information can be exposed externally.
Update to 2.4.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 'ocsinventory-server' . 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
-
1Identify exposure identify
grep -r 'ocsinventory-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ocsinventory-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ocsinventory-server to 2.4.1ステージング環境で 2.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory security-tracker.debian.org