ArchiSteamFarm is a C# application with primary purpose of idling Steam cards from multiple accounts simultaneously…
Summary
Vulnerability reported (CVE-2021-32794). Successful exploitation can lead to full system takeover. Exploitable via POST /Api/ASF.
Original description
The description as published by the source.
ArchiSteamFarm is a C# application with primary purpose of idling Steam cards from multiple accounts simultaneously. Due to a bug in ASF code POST /Api/ASF ASF API endpoint responsible for updating global ASF config incorrectly removed IPCPassword from the resulting config when the caller did not specify it explicitly. Due to the above, it was possible for the user to accidentally remove IPCPassword security measure from his IPC interface when updating global ASF config, which exists as part of global config update functionality in ASF-ui. Removal of IPCPassword possesses a security risk, as unauthorized users may in result access the IPC interface after such modification. The issue is patched in ASF V5.1.2.4 and future versions. We recommend to manually verify that IPCPassword is specified after update, and if not, set it accordingly. In default settings, ASF is configured to allow IPC access from localhost only and should not affect majority of users.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory 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-2021-32794 has been found.
Attackers can target a specific entry point like POST /Api/ASF over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2021-32794" on the vendor's site.
CVE-2021-32794
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /Api/ASF / IPCPassword / localhost
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) has been reported. Attackers reach the vulnerable code path via POST /Api/ASF.
Check the vendor advisory for the affected versions. Attack surface: POST /Api/ASF / IPCPassword / localhost.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /Api/ASF requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Hunt for indicators of compromise detect
grep 'POST /Api/ASF' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /Api/ASFへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /Api/ASF on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- patch github.com
- report github.com
- report steamcommunity.com