CVE-2022-23627

Inadequate access verification when using proxy commands in ArchiSteamFarm

MEDIUM
6.8
CVSS Score
Published: February 8, 2022 at 10:30 PM UTC
Updated: June 17, 2026 at 04:30 AM UTC
2 products affected across 2 vendorsArchisteamfarmArchiSteamFarm

Using ArchiSteamFarm by JustArchiNET?

Get instant alerts when new vulnerabilities affect ArchiSteamFarm - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.8
Exploit prediction
EPSS 1.0%
SSVC
No known exploit

Description

ArchiSteamFarm (ASF) is a C# application with primary purpose of idling Steam cards from multiple accounts simultaneously. Due to a bug in ASF code, introduced in version V5.2.2.2, the program didn't adequately verify effective access of the user sending proxy (i.e. `[Bots]`) commands. In particular, a proxy-like command sent to bot `A` targeting bot `B` has incorrectly verified user's access against bot `A` - instead of bot `B`, to which the command was originally designated. This in result allowed access to resources beyond those configured, being a security threat affecting confidentiality of other bot instances. A successful attack exploiting this bug requires a significant access granted explicitly by original owner of the ASF process prior to that, as attacker has to control at least a single bot in the process to make use of this inadequate access verification loophole. The issue is patched in ASF V5.2.2.5, V5.2.3.2 and future versions. Users are advised to update as soon as possible.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.2.2.2 ≤ v < 5.2.2.55.2.3.0 ≤ v < 5.2.3.2
Affected range stops below 5.2.2.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.2.3.2, so it looks safe — our inference, not a vendor statement
v < 5.2.2.5v < 5.2.3.2
Affected range stops below 5.2.2.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.2.3.2, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
HIGH
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-863

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card