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.

Threat-Mapped Scoring

Score: 1.8

Priority: P4 - Informational (Low)

• S9 – Sabotage of System/App

EPSS

Score: 0.73685
Percentile: 0.98741

CVSS Scoring

Mapped CWE(s)

• CWE-522 : Insufficiently Protected Credentials

All CAPEC(s)

CAPEC(s) with Mapped TTPs

Mapped ATT&CK TTPs

• T1552.004 : Private Keys
  Kill Chain: credential-access
• T1558.003 : Kerberoasting
  Kill Chain: credential-access
• T1543 : Create or Modify System Process
  Kill Chain: persistence
• T1021 : Remote Services
  Kill Chain: lateral-movement
• T1114.002 : Remote Email Collection
  Kill Chain: collection
• T1133 : External Remote Services
  Kill Chain: persistence
• T1078 : Valid Accounts
  Kill Chain: defense-evasion
• T1021.002 : SMB/Windows Admin Shares
  Kill Chain: lateral-movement
• T1110.004 : Credential Stuffing
  Kill Chain: credential-access
• T1550.002 : Pass the Hash
  Kill Chain: defense-evasion
• T1550.003 : Pass the Ticket
  Kill Chain: defense-evasion
• T1558 : Steal or Forge Kerberos Tickets
  Kill Chain: credential-access

Malware

APTs Threat Group Associations

Campaigns

Affected Products

• cpe:2.3:a:rpc.py_project:rpc.py:*:*:*:*:*:*:*:*

← Back to Home