GHSA-4C5C-2VC3-X5W2
Vulnerability from github – Published: 2026-06-05 15:24 – Updated: 2026-06-05 15:24Impact
If an attacker hacks into a vantage6 user's email account, they can 1) reset the password via email and then 2) reset the 2FA token via email. This way they reduce 2FA to 1FA (email access).
Note that most email providers require 2FA to access email, so this issue is not very likely to cause issues.
Proposed solution
Many web apps do not provide functionality to reset 2FA token (probably for this reason), but provide recovery codes as well. It would be better to provide these recovery codes to the user 1 time and then delete the option to reset it.
An alternative may be to only let server administrators reset 2FA token. However, this has as disadvantage that a hacked email account may send messages to the server admin to reset them, which they may fall for.
Patches
No
Workarounds
No
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "vantage6"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.0.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-27928"
],
"database_specific": {
"cwe_ids": [
"CWE-308"
],
"github_reviewed": true,
"github_reviewed_at": "2026-06-05T15:24:35Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "### Impact\nIf an attacker hacks into a vantage6 user\u0027s email account, they can 1) reset the password via email and then 2) reset the 2FA token via email. This way they reduce 2FA to 1FA (email access). \n\nNote that most email providers require 2FA to access email, so this issue is not very likely to cause issues.\n\n### Proposed solution\n\nMany web apps do not provide functionality to reset 2FA token (probably for this reason), but provide recovery codes as well. It would be better to provide these recovery codes to the user 1 time and then delete the option to reset it.\n\nAn alternative may be to only let server administrators reset 2FA token. However, this has as disadvantage that a hacked email account may send messages to the server admin to reset them, which they may fall for.\n\n### Patches\nNo\n\n### Workarounds\nNo",
"id": "GHSA-4c5c-2vc3-x5w2",
"modified": "2026-06-05T15:24:35Z",
"published": "2026-06-05T15:24:35Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/vantage6/vantage6/security/advisories/GHSA-4c5c-2vc3-x5w2"
},
{
"type": "WEB",
"url": "https://github.com/vantage6/vantage6/issues/1932"
},
{
"type": "PACKAGE",
"url": "https://github.com/vantage6/vantage6"
},
{
"type": "WEB",
"url": "https://github.com/vantage6/vantage6/blob/main/docs/release_notes.rst#500"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Vantage6: 2FA can be circumvented with hacked email access"
}
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.