PYSEC-2026-2005

Vulnerability from pysec - Published: 2026-07-07 11:45 - Updated: 2026-07-07 17:25
VLAI
Details

Impact

Much like https://github.com/vantage6/vantage6/security/advisories/GHSA-45gq-q4xh-cp53, it is possible to find which usernames exist in vantage6 by calling the API routes /recover/lost and /2fa/lost, which send emails to users if they have lost their password or MFA token. Usernames can be found by assessing response time differences, and additionally, they can be found because the endpoint gives a response "Failed to login" if the username exists.

Patches

No

Workarounds

No

Severity
5.3 (Medium)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Impacted products
Name purl
vantage6 pkg:pypi/vantage6
Aliases
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "vantage6",
        "purl": "pkg:pypi/vantage6"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.3.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.0.0",
        "0.0.0b0",
        "0.0.0b1",
        "0.0.0b3",
        "1.0.0",
        "1.0.0a1",
        "1.0.0a2",
        "1.0.0b10",
        "1.0.0b11",
        "1.0.0b12",
        "1.0.0b13",
        "1.0.0b14",
        "1.0.0b2",
        "1.0.0b3",
        "1.0.0b4",
        "1.0.0b5",
        "1.0.0b6",
        "1.0.0b7",
        "1.0.0b8",
        "1.0.0b9",
        "1.1.0",
        "1.1.0rc1",
        "1.1.0rc2",
        "1.2.0",
        "1.2.1",
        "1.2.2",
        "1.2.3",
        "1.2.3.post2",
        "2.0.0",
        "2.0.0.post1",
        "2.0.0a1",
        "2.0.0a2",
        "2.0.0a3",
        "2.0.1rc1",
        "2.0.1rc2",
        "2.1.0",
        "2.1.0rc1",
        "2.1.1",
        "2.2.0",
        "2.2.0b1",
        "2.2.0b2",
        "2.2.0b3",
        "2.2.0b4",
        "2.2.1",
        "2.2.10",
        "2.2.11",
        "2.2.12",
        "2.2.2",
        "2.2.3",
        "2.2.4",
        "2.2.5",
        "2.2.6",
        "2.2.7",
        "2.2.8",
        "2.2.9",
        "2.3.0",
        "2.3.0rc1",
        "2.3.0rc2",
        "2.3.0rc3",
        "2.3.0rc4",
        "2.3.0rc5",
        "2.3.1",
        "2.3.2",
        "2.3.2rc1",
        "2.3.3",
        "2.3.4",
        "2.3.5",
        "2.3.5b1",
        "3.0.0",
        "3.0.0b1",
        "3.0.0b2",
        "3.0.0b3",
        "3.0.0b4",
        "3.0.0b5",
        "3.0.0b6",
        "3.0.0b7",
        "3.0.0b8",
        "3.0.0rc1",
        "3.0.1",
        "3.0.2",
        "3.0.3",
        "3.0.4",
        "3.1.0",
        "3.1.0rc1",
        "3.1.0rc5",
        "3.1.0rc6",
        "3.1.0rc7",
        "3.1.0rc8",
        "3.1.0rc9",
        "3.1.1rc1",
        "3.1.1rc2",
        "3.10.0",
        "3.10.0rc1",
        "3.10.1",
        "3.10.3",
        "3.10.4",
        "3.11.0",
        "3.11.0rc1",
        "3.11.0rc2",
        "3.11.0rc3",
        "3.11.1",
        "3.2.0",
        "3.2.0rc1",
        "3.2.0rc2",
        "3.2.0rc3",
        "3.2.0rc4",
        "3.2.0rc5",
        "3.3.0",
        "3.3.0a0",
        "3.3.0rc1",
        "3.3.0rc2",
        "3.3.0rc3",
        "3.3.0rc4",
        "3.3.1",
        "3.3.2",
        "3.3.3",
        "3.3.4",
        "3.3.5",
        "3.3.6",
        "3.3.7",
        "3.3.7a2",
        "3.3.7a3",
        "3.3.8a1",
        "3.3.8a2",
        "3.3.8a4",
        "3.3.8a5",
        "3.3.8a6",
        "3.3.8a7",
        "3.3.8a8",
        "3.4.0",
        "3.4.0a1",
        "3.4.0a2",
        "3.4.0a3",
        "3.4.0a6",
        "3.4.1",
        "3.4.1a0",
        "3.4.1a1",
        "3.4.1a2",
        "3.4.1a3",
        "3.4.2",
        "3.4.2a0",
        "3.4.3",
        "3.5.0",
        "3.5.0rc1",
        "3.5.0rc2",
        "3.5.0rc3",
        "3.5.1",
        "3.5.2",
        "3.6.0",
        "3.6.1",
        "3.6.1rc1",
        "3.6.1rc2",
        "3.6.1rc3",
        "3.7.0",
        "3.7.0rc1",
        "3.7.0rc2",
        "3.7.1",
        "3.7.2",
        "3.7.3",
        "3.8.0",
        "3.8.0rc3",
        "3.8.1",
        "3.8.2",
        "3.8.2rc1",
        "3.8.3",
        "3.8.4",
        "3.8.5",
        "3.8.6",
        "3.8.7",
        "3.8.7rc1",
        "3.8.8",
        "3.8.8rc1",
        "3.8.8rc2",
        "3.8.8rc3",
        "3.9.0",
        "3.9.0rc2",
        "3.9.0rc4",
        "4.0.0",
        "4.0.0a10",
        "4.0.0a2",
        "4.0.0a3",
        "4.0.0a4",
        "4.0.0a5",
        "4.0.0a6",
        "4.0.0a7",
        "4.0.0a8",
        "4.0.0a9",
        "4.0.1",
        "4.0.1rc2",
        "4.0.2",
        "4.0.3",
        "4.1.0",
        "4.1.0b0",
        "4.1.0b1",
        "4.1.0rc0",
        "4.1.1",
        "4.1.2",
        "4.1.3",
        "4.2.0",
        "4.2.0rc1",
        "4.2.0rc2",
        "4.2.1",
        "4.2.2",
        "4.2.3",
        "4.3.0b3",
        "4.3.0b4",
        "4.3.0b5",
        "4.3.0b6",
        "4.3.0rc1",
        "4.3.0rc2"
      ]
    }
  ],
  "aliases": [
    "CVE-2024-24770",
    "GHSA-5h3x-6gwf-73jm"
  ],
  "details": "### Impact\nMuch like https://github.com/vantage6/vantage6/security/advisories/GHSA-45gq-q4xh-cp53, it is possible to find which usernames exist in vantage6 by calling the API routes `/recover/lost` and `/2fa/lost`, which send emails to users if they have lost their password or MFA token. Usernames can be found by assessing response time differences, and additionally, they can be found because the endpoint gives a response \"Failed to login\" if the username exists.\n\n### Patches\nNo\n\n### Workarounds\nNo",
  "id": "PYSEC-2026-2005",
  "modified": "2026-07-07T17:25:46.623216Z",
  "published": "2026-07-07T11:45:35.277562Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/vantage6/vantage6/security/advisories/GHSA-45gq-q4xh-cp53"
    },
    {
      "type": "WEB",
      "url": "https://github.com/vantage6/vantage6/security/advisories/GHSA-5h3x-6gwf-73jm"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-24770"
    },
    {
      "type": "WEB",
      "url": "https://github.com/vantage6/vantage6/commit/aecfd6d0e83165a41a60ebd52d2287b0217be26b"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/vantage6/vantage6"
    },
    {
      "type": "PACKAGE",
      "url": "https://pypi.org/project/vantage6"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-5h3x-6gwf-73jm"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "vantage6 vulnerable to a username timing attack on recover password/MFA token"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.


Detection rules are retrieved from Rulezet.