Vulnerability in uw-imap (DEBIAN-CVE-2018-19518)

Summary

Vulnerability in uw-imap (DEBIAN-CVE-2018-19518). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 8:2007f~dfsg-6 or later.

Original description

The description as published by the source.

University of Washington IMAP Toolkit 2007f on UNIX, as used in imap_open() in PHP and other products, launches an rsh command (by means of the imap_rimap function in c-client/imap4r1.c and the tcp_aopen function in osdep/unix/tcp_unix.c) without preventing argument injection, which might allow remote attackers to execute arbitrary OS commands if the IMAP server name is untrusted input (e.g., entered by a user of a web application) and if rsh has been replaced by a program with different argument semantics. For example, if rsh is a link to ssh (as seen on Debian and Ubuntu systems), then the attack can use an IMAP server name containing a "-oProxyCommand" argument.

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-19518 has been found in uw-imap.
Successful exploitation can lead to full system takeover.
What to do: upgrade uw-imap to 8:2007f~dfsg-6 or later.
If unsure, ask your IT team or search "uw-imap DEBIAN-CVE-2018-19518" on the vendor's site.

DEBIAN-CVE-2018-19518 (uw-imap)
Attack vector: remote (network-reachable) / no user interaction
Patched: 8:2007f~dfsg-6 — 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 uw-imap.

📍 Affected scope

Check the vendor advisory for the affected versions of uw-imap.

🔥 Severity

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

🔧 How to fix

Update to 8:2007f~dfsg-6.

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

Affected packages

Debian:12 uw-imap

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8:2007f~dfsg-6"}]}]

References

advisory security-tracker.debian.org