Vulnerability in Umlet (CVE-2018-1000548)

Summary

Vulnerability in Umlet (CVE-2018-1000548). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 14.3 or later.

Original description

The description as published by the source.

Umlet version < 14.3 contains a XML External Entity (XXE) vulnerability in File parsing that can result in disclosure of confidential data, denial of service, server side request forgery. This attack appear to be exploitable via Specially crafted UXF file. This vulnerability appears to have been fixed in 14.3.

Source: OSV.dev (Open Source Vulnerabilities) NVD 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 CVE-2018-1000548 has been found in Umlet.
Successful exploitation can lead to full system takeover.
What to do: upgrade Umlet to 14.3 or later.
If unsure, ask your IT team or search "Umlet CVE-2018-1000548" on the vendor's site.

CVE-2018-1000548 (Umlet)
Attack vector: local / unauthenticated
Patched: 14.3 — 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.

❓ What is the problem

A vulnerability (unclassified) exists in Umlet.

📍 Affected scope

Check the vendor advisory for the affected versions of Umlet.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 14.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Umlet' . 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 exposure identify
```
grep -r 'Umlet' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Umlet を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade Umlet to 14.3
```
ステージング環境で 14.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

Ubuntu UBUNTU-CVE-2018-1000548 umlet

References

report 0dd.zone
report github.com