Pega Infinity: Deserialization of Untrusted Data
CVE-2022-24082 is a critical-severity deserialization of untrusted data vulnerability in Pega Infinity from Pegasystems, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 8.7.3 as the first without the flaw, so updating Pega Infinity to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 12.2% chance of exploitation within 30 days, which is in the top 3.77% of all scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Pega Infinity to 8.7.3 or a later version.
- Update Infinity to 8.7.3 or a later version.
- Read the advisory on support.pega.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Pegasystems | Pega Infinity | 8.1.0; before 8.7.3 | 8.7.3 |
| Pega | Infinity | 8.1.0 up to, but not including, 8.7.3 | 8.7.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 3.0 | 9.8 | Critical | CNA (pega.com) |
Official description
If an on-premise installation of the Pega Platform is configured with the port for the JMX interface exposed to the Internet and port filtering is not properly configured, then it may be possible to upload serialized payloads to attack the underlying system. This does not affect systems running on PegaCloud due to its design and architecture.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Deserialization of Untrusted Data
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
How developers prevent this class of flaw
- If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
- When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
- Explicitly define a final object() to prevent deserialization.
More Deserialization of Untrusted Data vulnerabilities (CWE-502)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
Technical write-ups (may include proof of concept)
- packetstormsecurity.com/files/169480/Pega-Platform-8.7.3-Remote-Code-Execution.htmlExploit, Third Party Advisory, VDB Entry
Other vulnerabilities in Pega Infinity
- 8.8 High severity
- 8.6 High severity
- 7.1 High severity
Recent Deserialization of Untrusted Data vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.