Approved changes feed: RSS · Atom
cpe:2.3:a:rpc.py_project:rpc.py:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Rpc.Py Project (c998551f-b155-5a29-b4bb-0d6ad748dd79) |
|---|---|
| Product | Rpc.Py (919dda25-5c58-5c00-afab-87250e01419c) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/abersheeran/rpc.py |
purl2cpe | 2026-06-01 10:13:32.246888 |
pkg:pypi/rpc.py |
purl2cpe | 2026-06-01 10:13:32.246892 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-35411 |
vulnerable | 2026-06-08 05:46:04.870229 |
Details available
rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the "serializer: pickle" HTTP header is sent. In other words, although JSON (not Pickle) is the default data format, an unauthenticated client can cause the data to be processed with unpickle.
Published: 2022-07-08T18:07:40.000Z
Updated: 2024-08-03T09:36:44.447Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.