Skip to content

Commit d11c246

Browse files
1 parent 141c234 commit d11c246

3 files changed

Lines changed: 130 additions & 5 deletions

File tree

advisories/unreviewed/2026/03/GHSA-2jpr-83rg-v67j/GHSA-2jpr-83rg-v67j.json renamed to advisories/github-reviewed/2026/03/GHSA-2jpr-83rg-v67j/GHSA-2jpr-83rg-v67j.json

Lines changed: 30 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,12 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-2jpr-83rg-v67j",
4-
"modified": "2026-03-05T06:30:27Z",
4+
"modified": "2026-03-05T21:15:25Z",
55
"published": "2026-03-05T06:30:27Z",
66
"aliases": [
77
"CVE-2026-27982"
88
],
9+
"summary": "django-allauth has an open redirect vulnerability",
910
"details": "An open redirect vulnerability exists in django-allauth versions prior to 65.14.1 when SAML IdP initiated SSO is enabled (it is disabled by default), which may allow an attacker to redirect users to an arbitrary external website via a crafted URL.",
1011
"severity": [
1112
{
@@ -14,10 +15,30 @@
1415
},
1516
{
1617
"type": "CVSS_V4",
17-
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
18+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N"
19+
}
20+
],
21+
"affected": [
22+
{
23+
"package": {
24+
"ecosystem": "PyPI",
25+
"name": "django-allauth"
26+
},
27+
"ranges": [
28+
{
29+
"type": "ECOSYSTEM",
30+
"events": [
31+
{
32+
"introduced": "0"
33+
},
34+
{
35+
"fixed": "65.14.1"
36+
}
37+
]
38+
}
39+
]
1840
}
1941
],
20-
"affected": [],
2142
"references": [
2243
{
2344
"type": "ADVISORY",
@@ -27,6 +48,10 @@
2748
"type": "WEB",
2849
"url": "https://allauth.org/news/2026/02/django-allauth-65.14.1-released"
2950
},
51+
{
52+
"type": "PACKAGE",
53+
"url": "https://github.com/pennersr/django-allauth"
54+
},
3055
{
3156
"type": "WEB",
3257
"url": "https://jvn.jp/en/jp/JVN23669411"
@@ -37,8 +62,8 @@
3762
"CWE-601"
3863
],
3964
"severity": "MODERATE",
40-
"github_reviewed": false,
41-
"github_reviewed_at": null,
65+
"github_reviewed": true,
66+
"github_reviewed_at": "2026-03-05T21:15:25Z",
4267
"nvd_published_at": "2026-03-05T06:16:30Z"
4368
}
4469
}
Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-7rhv-h82h-vpjh",
4+
"modified": "2026-03-05T21:14:57Z",
5+
"published": "2026-03-05T21:14:57Z",
6+
"aliases": [],
7+
"summary": "EC-CUBE has a Vulnerability that Allows MFA Bypass in the Administrative Interface",
8+
"details": "# Vulnerability Allowing MFA Bypass\n\n## Affected EC-CUBE Versions\nVersions: 4.1.0 – 4.3.1\n\n## Vulnerability Overview\nIf an administrator’s ID and password are compromised, an issue exists that allows an attacker to bypass the normally required two-factor authentication (2FA) and log in to the administrative interface.\n\n## Severity and Impact\n\n**CVSS v3.1 score** \nBase score: 6.2 / Temporal score: 5.7 / Environmental score (after mitigation and countermeasures): 0.0\n\nAn attacker can forcibly overwrite the 2FA configuration of an account with administrative privileges. As a result, the legitimate administrator can be locked out, while the attacker can log in to the administrative interface and perform unauthorized actions such as viewing sensitive information or tampering with the website.\n\n## Root Cause Details\n\nThere are flaws in the access control implementation for the 2FA settings page (`/admin/two_factor_auth/set`).\n\n1. **TwoFactorAuthListener.php** \n The route for the 2FA settings page (`admin_two_factor_auth_set`) is included in the list of routes excluded from the 2FA authentication check.\n\n2. **TwoFactorAuthController.php** \n Even for users who already have 2FA configured, the implementation allows reconfiguration (overwriting) of the 2FA secret key without passing 2FA authentication.\n\n## Attack Preconditions and Steps\n\n**Preconditions:**\n- The attacker knows the administrative user’s ID and password.\n- 2FA is enabled for that user.\n\n**Attack Steps:**\n1. Attempt to log in using the ID and password.\n2. When the 2FA code entry screen is displayed, do not enter a code; instead, directly modify the URL to access `/admin/two_factor_auth/set`.\n3. Because access is not denied, the attacker can generate and save (overwrite) a new 2FA secret key.\n\n\n# MFAバイパスが可能な脆弱性\n\n## EC-CUBEバージョン\nバージョン: 4.1.0 ~ 4.3.1\n\n## 脆弱性の概要\n管理者のIDとパスワードが漏洩している場合、本来必要な2段階認証を回避して管理画面にログインできてしまう問題です。\n\n## 深刻度と影響\n\nCVSS3.1スコア:基本評価:6.2 / 現状評価:5.7 / 環境評価(緩和・対策後):0.0 \n\n攻撃者は管理者権限を持つアカウントの2FA設定を強制的に上書きできます。これにより、正規の管理者を締め出しつつ、攻撃者自身が管理画面へログインし、機密情報の閲覧やWebサイトの改ざんなどの不正操作を行うことが可能になります。\n\n## 脆弱性の詳細な原因\n\nシステムの実装において、2FA設定画面(/admin/two_factor_auth/set)へのアクセス制御に不備があり。\n\n1. TwoFactorAuthListener.php\n2FA認証チェックを除外するルート設定に、設定画面(admin_two_factor_auth_set)が含まれている。\n2. TwoFactorAuthController.php\n既に2FA設定済みのユーザーであっても、2FA認証を通過せずに新しい鍵の再設定(上書き)を受け入れてしまう仕様になっている。\n\n## 攻撃の成立条件と手順\n\n前提条件:\n管理ユーザーのIDとパスワードを知っていること。\nそのユーザーで2FAが有効化されていること。\n\n攻撃手順:\n\n1. IDとパスワードでログインを試行する。\n2. 2FAコード入力画面が表示されるが、入力を行わずに直接URLを書き換えて /admin/two_factor_auth/set へアクセスする。\n3. アクセスが拒否されないため、攻撃者は新しい2FA秘密鍵を発行し、保存(上書き)する。\n4. 以降、攻撃者が作成した新しい2FAコードを使ってログインが可能になる。",
9+
"severity": [
10+
{
11+
"type": "CVSS_V3",
12+
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L"
13+
}
14+
],
15+
"affected": [
16+
{
17+
"package": {
18+
"ecosystem": "Packagist",
19+
"name": "ec-cube/ec-cube"
20+
},
21+
"ranges": [
22+
{
23+
"type": "ECOSYSTEM",
24+
"events": [
25+
{
26+
"introduced": "4.1.0"
27+
},
28+
{
29+
"last_affected": "4.3.1"
30+
}
31+
]
32+
}
33+
]
34+
}
35+
],
36+
"references": [
37+
{
38+
"type": "WEB",
39+
"url": "https://github.com/EC-CUBE/ec-cube/security/advisories/GHSA-7rhv-h82h-vpjh"
40+
},
41+
{
42+
"type": "WEB",
43+
"url": "https://github.com/EC-CUBE/ec-cube/commit/094785943bfc3815c29f0cce9dbabb9bcc688474"
44+
},
45+
{
46+
"type": "PACKAGE",
47+
"url": "https://github.com/EC-CUBE/ec-cube"
48+
}
49+
],
50+
"database_specific": {
51+
"cwe_ids": [
52+
"CWE-287"
53+
],
54+
"severity": "MODERATE",
55+
"github_reviewed": true,
56+
"github_reviewed_at": "2026-03-05T21:14:57Z",
57+
"nvd_published_at": null
58+
}
59+
}
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-mh23-rw7f-v5pq",
4+
"modified": "2026-03-05T21:15:45Z",
5+
"published": "2026-03-05T21:15:45Z",
6+
"aliases": [],
7+
"summary": "`time-sync` was removed from crates.io due to malicious code",
8+
"details": "The `time-sync` crate attempted to exfiltrate `.env` files to a server that was in turn impersonating the legitimate `timeapi.io` service. This the same attack that we've seen three times in the last few days.\n\nThe malicious crate had 1 version published on 2026-03-04 approximately 50 minutes before removal and had no evidence of actual downloads. There were no crates depending on this crate on crates.io.",
9+
"severity": [],
10+
"affected": [
11+
{
12+
"package": {
13+
"ecosystem": "crates.io",
14+
"name": "time-sync"
15+
},
16+
"ranges": [
17+
{
18+
"type": "ECOSYSTEM",
19+
"events": [
20+
{
21+
"introduced": "0"
22+
}
23+
]
24+
}
25+
]
26+
}
27+
],
28+
"references": [
29+
{
30+
"type": "WEB",
31+
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0036.html"
32+
}
33+
],
34+
"database_specific": {
35+
"cwe_ids": [],
36+
"severity": "CRITICAL",
37+
"github_reviewed": true,
38+
"github_reviewed_at": "2026-03-05T21:15:45Z",
39+
"nvd_published_at": null
40+
}
41+
}

0 commit comments

Comments
 (0)