Skip to content

Commit 8da6cca

Browse files
1 parent 7c5d0fc commit 8da6cca

2 files changed

Lines changed: 25 additions & 9 deletions

File tree

advisories/github-reviewed/2026/03/GHSA-73f9-jhhh-hr5m/GHSA-73f9-jhhh-hr5m.json

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-73f9-jhhh-hr5m",
4-
"modified": "2026-03-23T21:18:56Z",
4+
"modified": "2026-03-25T20:35:28Z",
55
"published": "2026-03-23T21:18:56Z",
66
"aliases": [
77
"CVE-2026-33202"
@@ -78,6 +78,10 @@
7878
"type": "WEB",
7979
"url": "https://github.com/rails/rails/security/advisories/GHSA-73f9-jhhh-hr5m"
8080
},
81+
{
82+
"type": "ADVISORY",
83+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33202"
84+
},
8185
{
8286
"type": "WEB",
8387
"url": "https://github.com/rails/rails/commit/8c9676b803820110548cdb7523800db43bc6874c"
@@ -114,6 +118,6 @@
114118
"severity": "MODERATE",
115119
"github_reviewed": true,
116120
"github_reviewed_at": "2026-03-23T21:18:56Z",
117-
"nvd_published_at": null
121+
"nvd_published_at": "2026-03-24T00:16:29Z"
118122
}
119123
}

advisories/github-reviewed/2026/03/GHSA-p747-qc5p-773r/GHSA-p747-qc5p-773r.json

Lines changed: 19 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-p747-qc5p-773r",
4-
"modified": "2026-03-20T20:43:00Z",
4+
"modified": "2026-03-25T20:34:07Z",
55
"published": "2026-03-20T20:43:00Z",
66
"aliases": [
77
"CVE-2026-33473"
88
],
99
"summary": "Vikunja has TOTP Reuse During Validity Window",
10-
"details": "### Summary\nAny user that has enabled 2FA can have their TOTP reused during the standard 30 second validity window.\n\n### Details\nThe below code is called when a user that has 2FA is authenticating to the application. Once they submit a valid username-password-totp combination, the user gets authenticated. If that same TOTP is used for the same user's account again within the validity window, it will allow the other session to authenticate successfully.\n\n**Source**: <ins>pkg/user/totp.go:128</ins>\n```go\n// ValidateTOTPPasscode validated totp codes of users.\nfunc ValidateTOTPPasscode(s *xorm.Session, passcode *TOTPPasscode) (t *TOTP, err error) {\n\tt, err = GetTOTPForUser(s, passcode.User)\n\tif err != nil {\n\t\treturn\n\t}\n\n\tif !totp.Validate(passcode.Passcode, t.Secret) {\n\t\treturn nil, ErrInvalidTOTPPasscode{Passcode: passcode.Passcode}\n\t}\n\n\treturn\n}\n```\n\nSection 6.5.1 within the [Authentication](https://github.com/OWASP/ASVS/blob/master/5.0/en/0x15-V6-Authentication.md) section of the OWASP ASVS recommends multiple checks, some of which involving TOTPs:\n\n> Verify that lookup secrets, out-of-band authentication requests or codes, and time-based one-time passwords (TOTPs) are only successfully usable once.\n\nThe OWASP WSTG also references this as one of their [checks](https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/04-Authentication_Testing/11-Testing_Multi-Factor_Authentication) to look for:\n\n> Can the OTPs be used more than once?\n\n### PoC\n\nhttps://github.com/user-attachments/assets/19d3b4c3-c219-4f59-b57d-45c9f6a264c8\n\n### Impact\nAny user who uses 2FA could be impacted if their traffic is able to be captured, they're phished/social engineered, or other methods of attack. This disrupts one layer of the defense-in-depth model surrounding 2FA.\n\n### Remediation\n\nStore a deny-list of TOTP codes for their validity windows and check submitted codes against it to ensure none are being reused. After their validity window has closed, the 2FA code can be removed from the list.",
10+
"details": "### Summary\nAny user that has enabled 2FA can have their TOTP reused during the standard 30 second validity window.\n\n### Details\nThe below code is called when a user that has 2FA is authenticating to the application. Once they submit a valid username-password-totp combination, the user gets authenticated. If that same TOTP is used for the same user's account again within the validity window, it will allow the other session to authenticate successfully.\n\n**Source**: <ins>pkg/user/totp.go:128</ins>\n```go\n// ValidateTOTPPasscode validated totp codes of users.\nfunc ValidateTOTPPasscode(s *xorm.Session, passcode *TOTPPasscode) (t *TOTP, err error) {\n\tt, err = GetTOTPForUser(s, passcode.User)\n\tif err != nil {\n\t\treturn\n\t}\n\n\tif !totp.Validate(passcode.Passcode, t.Secret) {\n\t\treturn nil, ErrInvalidTOTPPasscode{Passcode: passcode.Passcode}\n\t}\n\n\treturn\n}\n```\n\nSection 6.5.1 within the [Authentication](https://github.com/OWASP/ASVS/blob/master/5.0/en/0x15-V6-Authentication.md) section of the OWASP ASVS recommends multiple checks, some of which involving TOTPs:\n\n> Verify that lookup secrets, out-of-band authentication requests or codes, and time-based one-time passwords (TOTPs) are only successfully usable once.\n\nThe OWASP WSTG also references this as one of their [checks](https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/04-Authentication_Testing/11-Testing_Multi-Factor_Authentication) to look for:\n\n> Can the OTPs be used more than once?\n\n### PoC\n\nhttps://github.com/user-attachments/assets/19d3b4c3-c219-4f59-b57d-45c9f6a264c8\n\n### Impact\nAny user who uses 2FA could be impacted if their traffic is able to be captured, they're phished/social engineered, or other methods of attack. This disrupts one layer of the defense-in-depth model surrounding 2FA.\n\n### Similar CVEs\n\n- [CVE-2025-6014](https://nvd.nist.gov/vuln/detail/CVE-2025-6014)\n- [CVE-2025-55003](https://nvd.nist.gov/vuln/detail/CVE-2025-55003)\n\n### Remediation\n\nStore a deny-list of TOTP codes for their validity windows and check submitted codes against it to ensure none are being reused. After their validity window has closed, the 2FA code can be removed from the list.",
1111
"severity": [
1212
{
1313
"type": "CVSS_V3",
@@ -26,23 +26,35 @@
2626
"events": [
2727
{
2828
"introduced": "0.13"
29-
},
30-
{
31-
"last_affected": "2.1.0"
3229
}
3330
]
3431
}
35-
]
32+
],
33+
"database_specific": {
34+
"last_known_affected_version_range": "< 2.2.1"
35+
}
3636
}
3737
],
3838
"references": [
3939
{
4040
"type": "WEB",
4141
"url": "https://github.com/go-vikunja/vikunja/security/advisories/GHSA-p747-qc5p-773r"
4242
},
43+
{
44+
"type": "ADVISORY",
45+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33473"
46+
},
4347
{
4448
"type": "PACKAGE",
4549
"url": "https://github.com/go-vikunja/vikunja"
50+
},
51+
{
52+
"type": "WEB",
53+
"url": "https://vikunja.io/changelog/vikunja-v2.2.0-was-released"
54+
},
55+
{
56+
"type": "WEB",
57+
"url": "https://vikunja.io/changelog/vikunja-v2.2.2-was-released"
4658
}
4759
],
4860
"database_specific": {
@@ -52,6 +64,6 @@
5264
"severity": "MODERATE",
5365
"github_reviewed": true,
5466
"github_reviewed_at": "2026-03-20T20:43:00Z",
55-
"nvd_published_at": null
67+
"nvd_published_at": "2026-03-24T16:16:33Z"
5668
}
5769
}

0 commit comments

Comments
 (0)