CVE-2019-16328: Dynamic modification of RPyC service due to missing security check

CVE-2019-16328 · Severity: low · CVSS 3.1 · Published 2019-10-03

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.

Technologies: rpyc (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2019-16328 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-16328 being exploited in the wild.
How severe is CVE-2019-16328?
Low severity, with a CVSS score of 3.1, published 3 October 2019.
Which products and versions are affected?
rpyc (PyPI) ECOSYSTEM:introduced=4.1.0,fixed=4.1.1, ECOSYSTEM:introduced=4.1.0,fixed=4.1.2.
Is there a fix for CVE-2019-16328?
Yes. rpyc (PyPI): upgrade to 4.1.1, 4.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-16328?
Check whether you run rpyc (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • rpyc (PyPI): upgrade to 4.1.1, 4.1.2 or later
    pip install "rpyc>=4.1.2"

Affected products

  • rpyc (PyPI) ECOSYSTEM:introduced=4.1.0,fixed=4.1.1, ECOSYSTEM:introduced=4.1.0,fixed=4.1.2

Identifiers

  • CVE-2019-16328
  • GHSA-9ggp-4jpr-7ppj
  • GHSA-pj4g-4488-wmxm
  • PYSEC-2019-118

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.