CVE-2019-16328

Exp

In RPyC 4.1.x through 4.1.1, a remote attacker can dynamically modify object attributes to construct a remote procedure call that executes code for an RPyC service with default configuration settings.

Published: 2019-10-03 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-16328 is rated High Exploit Risk (84.6/100): CVSS High severity, with high exploitation likelihood (EPSS 73.04%, 99th percentile). 1 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +22.20% over the last day, indicating growing attacker interest. Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2019-16328

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2019-16328

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 50.84% 73.04% +22.20%
2 2025-11-18 73.04% 50.84% -22.20%
3 2025-06-23 — 73.04% —

Full EPSS history (21 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-16328

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2019-16328

GitHub Security Advisory for CVE-2019-16328

GHSA-pj4g-4488-wmxm · Severity: high · Ecosystem: pip — Dynamic modification of RPyC service due to missing security check

OS Trackers for CVE-2019-16328

vendor priority summary link
debian unimportant CVE-2019-16328 unimportant priority: Debian including 1 source packages (rpyc), 4 status rows across 4 suites (bookworm, forky, sid, trixie): resolved 4. https://security-tracker.debian.org/tracker/CVE-2019-16328
ubuntu medium CVE-2019-16328 medium priority: Ubuntu including 1 source packages (rpyc), 6 status rows across 6 suites (bionic, focal, groovy, trusty, upstream, xenial): DNE 4, not-affected 1, released 1. https://ubuntu.com/security/CVE-2019-16328

Affected software / configurations for CVE-2019-16328

Vendor Product Version Raw CPE
rpyc_project rpyc >= 4.1.0, <= 4.1.1 cpe:2.3:a:rpyc_project:rpyc:*:*:*:*:*:*:*:*

References for CVE-2019-16328

cvelogic Threat Intelligence