PYSEC-2026-900

Vulnerability from pysec - Published: 2026-07-07 10:17 - Updated: 2026-07-07 11:31
VLAI
Details

The collection remote for pulp_ansible stores tokens in plaintext instead of using pulp's encrypted field and exposes them in read/write mode via the API () instead of marking it as write only.

Impacted products
Name purl
pulp-ansible pkg:pypi/pulp-ansible

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "pulp-ansible",
        "purl": "pkg:pypi/pulp-ansible"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.15.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.0.1b1",
        "0.1.0b2",
        "0.1.0rc1",
        "0.1.0rc2",
        "0.1.0rc3",
        "0.1.0rc4",
        "0.1.0rc5",
        "0.10.0",
        "0.10.1",
        "0.10.2",
        "0.10.3",
        "0.10.4",
        "0.10.5",
        "0.11.0",
        "0.11.1",
        "0.12.0",
        "0.12.1",
        "0.13.0",
        "0.13.1",
        "0.13.2",
        "0.13.4",
        "0.13.5",
        "0.13.6",
        "0.14.0",
        "0.14.1",
        "0.14.2",
        "0.2.0",
        "0.2.0b1",
        "0.2.0b10",
        "0.2.0b11",
        "0.2.0b12",
        "0.2.0b13",
        "0.2.0b14",
        "0.2.0b15",
        "0.2.0b2",
        "0.2.0b3",
        "0.2.0b4",
        "0.2.0b5",
        "0.2.0b6",
        "0.2.0b7",
        "0.2.0b8",
        "0.2.0b9",
        "0.3.0",
        "0.4.0",
        "0.4.1",
        "0.4.2",
        "0.4.3",
        "0.5.0",
        "0.5.1",
        "0.5.10",
        "0.5.11",
        "0.5.2",
        "0.5.3",
        "0.5.4",
        "0.5.5",
        "0.5.6",
        "0.5.7",
        "0.5.8",
        "0.5.9",
        "0.6.0",
        "0.6.1",
        "0.6.2",
        "0.7.0",
        "0.7.1",
        "0.7.2",
        "0.7.3",
        "0.7.4",
        "0.7.5",
        "0.7.6",
        "0.8.0",
        "0.8.1",
        "0.9.0",
        "0.9.1",
        "0.9.2"
      ]
    }
  ],
  "aliases": [
    "CVE-2022-3644",
    "GHSA-qv37-mfjf-42h8"
  ],
  "details": "The collection remote for pulp_ansible stores tokens in plaintext instead of using pulp\u0027s encrypted field and exposes them in read/write mode via the API () instead of marking it as write only. ",
  "id": "PYSEC-2026-900",
  "modified": "2026-07-07T11:31:01.821621Z",
  "published": "2026-07-07T10:17:22.799524Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-3644"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pulp/pulp_ansible/issues/1221"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pulp/pulp_ansible/commit/d13c427b09482a7f598d8ee597d17a8a34888665"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/pulp/pulp_ansible"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pulp/pulp_ansible/blob/main/pulp_ansible/app/models.py#L234"
    },
    {
      "type": "PACKAGE",
      "url": "https://pypi.org/project/pulp-ansible"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-qv37-mfjf-42h8"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Plaintext storage of tokens in pulp_ansible"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…