Vulnerability DatabaseGHSA-jjgp-whrp-gq8m

GHSA-jjgp-whrp-gq8m
Python vulnerability analysis and mitigation

Overview

The vulnerability (GHSA-jjgp-whrp-gq8m) affects the in-toto package (pip) versions <= 1.4.0 and involves multiple concerns about how in-toto uses PGP keys. This moderate severity vulnerability was discovered and published on May 10, 2023, with the latest update on May 11, 2023. The issue primarily relates to incomplete implementation of PGP trust model validations in the software (GitHub Advisory).

Technical details

The vulnerability encompasses three main technical issues: 1) PGP Key Creation Time Not Validated (low severity) - the system doesn't verify if the validity period of a PGP Key is in the future when copying from GnuPG to a layout or during signature verification, 2) PGP Key Revocation Not Considered (medium severity) - the system doesn't check PGP revocation signatures during key copying or signature verification, and 3) PGP Key Usage Flags Not Considered (low severity) - the system doesn't verify PGP usage flags during key operations. The vulnerability is classified under CWE-295 (GitHub Advisory).

Impact

The vulnerability could allow a MITM attacker who can manipulate delivered software products to potentially control the system time through NTP manipulation. In a specific scenario, an attacker with control over two expired subkeys with non-overlapping validity periods could set the system time to accept both keys. Additionally, revoked keys might still be accepted for signatures, and keys may be used for signing even when not permitted by their usage flags (GitHub Advisory).

Mitigation and workarounds

The project has decided not to implement full PGP trust model verification as in-toto doesn't rely on PGP's trust model and shouldn't require consultation with a separate PKI/web-of-trust at verification time. Instead, the preferred mitigation strategy is to verify these properties when exporting a public key from GnuPG and to clarify in documentation that no verification against the PGP trust model is performed afterward. Project owners are responsible for establishing trust by adding PGP public keys to layouts and revoking layouts if keys are no longer trusted (GitHub Advisory).

Additional resources


SourceThis report was generated using AI

Related Python vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2025-67511CRITICAL9.6
  • PythonPython
  • cai-framework
NoNoDec 11, 2025
CVE-2025-13780CRITICAL9.1
  • PythonPython
  • cpe:2.3:a:pgadmin:pgadmin
NoYesDec 11, 2025
CVE-2025-67644HIGH7.3
  • PythonPython
  • langgraph-checkpoint-sqlite
NoYesDec 11, 2025
CVE-2025-67720MEDIUM6.5
  • PythonPython
  • pyrofork
NoYesDec 11, 2025
CVE-2025-67485MEDIUM5.3
  • PythonPython
  • mad-proxy
NoNoDec 10, 2025

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management