Vulnerability in engrampa (UBUNTU-CVE-2023-52138)

Summary

Vulnerability in engrampa (UBUNTU-CVE-2023-52138). Data can be tampered with by attackers. Mitigation: upgrade to 1.12.0-2ubuntu0.1+esm1 or later.

Original description

The description as published by the source.

Engrampa is an archive manager for the MATE environment. Engrampa is found to be vulnerable to a Path Traversal vulnerability that can be leveraged to achieve full Remote Command Execution (RCE) on the target. While handling CPIO archives, the Engrampa Archive manager follows symlink, cpio by default will follow stored symlinks while extracting and the Archiver will not check the symlink location, which leads to arbitrary file writes to unintended locations. When the victim extracts the archive, the attacker can craft a malicious cpio or ISO archive to achieve RCE on the target system. This vulnerability was fixed in commit 63d5dfa.

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 UBUNTU-CVE-2023-52138 has been found in engrampa.
Data can be tampered with by attackers.
What to do: upgrade engrampa to 1.12.0-2ubuntu0.1+esm1 or later.
If unsure, ask your IT team or search "engrampa UBUNTU-CVE-2023-52138" on the vendor's site.

UBUNTU-CVE-2023-52138 (engrampa)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.12.0-2ubuntu0.1+esm1 — 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 engrampa.

📍 Affected scope

Check the vendor advisory for the affected versions of engrampa.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to 1.12.0-2ubuntu0.1+esm1.

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

Affected packages

Ubuntu:Pro:16.04:LTS engrampa

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.12.0-2ubuntu0.1+esm1"}]}]

Ubuntu:Pro:18.04:LTS engrampa

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.20.0-1ubuntu0.1~esm1"}]}]

Ubuntu:Pro:20.04:LTS engrampa

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.24.0-2ubuntu0.1~esm1"}]}]

Ubuntu:Pro:22.04:LTS engrampa

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.26.0-1ubuntu1+esm1"}]}]

References

advisory ubuntu.com
report ubuntu.com
report github.com
report github.com
report cve.org