LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35411: rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the "serializer: pickle"...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2022-35411 is an unauthenticated remote code execution issue in rpc.py through 0.6.0. A client can request Pickle handling via an HTTP header, causing unsafe unpickling even though JSON is the default. Any exposed service using affected rpc.py versions should be treated as high risk. Exposure is limited to applications or services using rpc.py through 0.6.0, especially RPC endpoints reachable by unauthenticated clients over HTTP. The source bundle does not identify specific vendors, packaged products, CPEs, or deployment prevalence. Prioritize investigation where rpc.py is internet-facing or reachable from untrusted networks. The business urgency is high because the described condition enables remote code execution, but scope is uncertain because the source bundle lacks product metadata and exploitation confirmation. Mitigation focus: Identify any use of rpc.py through 0.6.0.; Review the referenced upstream commit and vendor/project guidance.; Upgrade or patch according to confirmed upstream guidance..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-35411 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.