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.
6002 vulnerabilities reference this CWE, most recent first.
GHSA-5MH8-87HF-R6J9
Vulnerability from github – Published: 2022-05-01 23:36 – Updated: 2022-05-01 23:36Unspecified vulnerability in IBM WebSphere MQ 6.0.x before 6.0.2.2 and 5.3 before Fix Pack 14 allows attackers to bypass access restrictions for a queue manager via a SVRCONN (MQ client) channel.
{
"affected": [],
"aliases": [
"CVE-2008-1130"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2008-03-04T00:44:00Z",
"severity": "MODERATE"
},
"details": "Unspecified vulnerability in IBM WebSphere MQ 6.0.x before 6.0.2.2 and 5.3 before Fix Pack 14 allows attackers to bypass access restrictions for a queue manager via a SVRCONN (MQ client) channel.",
"id": "GHSA-5mh8-87hf-r6j9",
"modified": "2022-05-01T23:36:52Z",
"published": "2022-05-01T23:36:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-1130"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/29170"
},
{
"type": "WEB",
"url": "http://www-1.ibm.com/support/docview.wss?rs=171\u0026uid=swg1IZ01272"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/28046"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id?1019527"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2008/0719"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-5MJ3-RRXF-HQRV
Vulnerability from github – Published: 2022-05-24 19:13 – Updated: 2022-07-13 00:01api/account/register in the TH Wildau COVID-19 Contact Tracing application through 2021-09-01 has Incorrect Access Control. An attacker can interfere with tracing of infection chains by creating 500 random users within 2500 seconds.
{
"affected": [],
"aliases": [
"CVE-2021-33831"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-09-07T06:15:00Z",
"severity": "MODERATE"
},
"details": "api/account/register in the TH Wildau COVID-19 Contact Tracing application through 2021-09-01 has Incorrect Access Control. An attacker can interfere with tracing of infection chains by creating 500 random users within 2500 seconds.",
"id": "GHSA-5mj3-rrxf-hqrv",
"modified": "2022-07-13T00:01:26Z",
"published": "2022-05-24T19:13:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-33831"
},
{
"type": "WEB",
"url": "https://github.com/lanmarc77/CVE-2021-33831"
},
{
"type": "WEB",
"url": "https://www.th-wildau.de/studieren-weiterbilden/neuigkeiten-und-veranstaltungen/corona"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-5MPG-RWCJ-R8CJ
Vulnerability from github – Published: 2023-11-27 18:31 – Updated: 2023-11-27 18:31An authentication bypass exists in Arcserve UDP prior to version 9.2. An unauthenticated, remote attacker can obtain a valid authentication identifier that allows them to authenticate to the management console and perform tasks that require authentication.
{
"affected": [],
"aliases": [
"CVE-2023-41999"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-11-27T17:15:07Z",
"severity": "HIGH"
},
"details": "An authentication bypass exists in Arcserve UDP prior to version 9.2. An unauthenticated, remote attacker can obtain a valid authentication identifier that allows them to authenticate to the management console and perform tasks that require authentication.",
"id": "GHSA-5mpg-rwcj-r8cj",
"modified": "2023-11-27T18:31:13Z",
"published": "2023-11-27T18:31:13Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-41999"
},
{
"type": "WEB",
"url": "https://www.tenable.com/security/research/tra-2023-37"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-5MRF-XH4H-R8WX
Vulnerability from github – Published: 2022-05-01 23:45 – Updated: 2025-04-09 03:54The _gnutls_recv_client_kx_message function in lib/gnutls_kx.c in libgnutls in gnutls-serv in GnuTLS before 2.2.4 continues to process Client Hello messages within a TLS message after one has already been processed, which allows remote attackers to cause a denial of service (NULL dereference and crash) via a TLS message containing multiple Client Hello messages, aka GNUTLS-SA-2008-1-2.
{
"affected": [],
"aliases": [
"CVE-2008-1949"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2008-05-21T13:24:00Z",
"severity": "HIGH"
},
"details": "The _gnutls_recv_client_kx_message function in lib/gnutls_kx.c in libgnutls in gnutls-serv in GnuTLS before 2.2.4 continues to process Client Hello messages within a TLS message after one has already been processed, which allows remote attackers to cause a denial of service (NULL dereference and crash) via a TLS message containing multiple Client Hello messages, aka GNUTLS-SA-2008-1-2.",
"id": "GHSA-5mrf-xh4h-r8wx",
"modified": "2025-04-09T03:54:48Z",
"published": "2022-05-01T23:45:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-1949"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/42530"
},
{
"type": "WEB",
"url": "https://issues.rpath.com/browse/RPL-2552"
},
{
"type": "WEB",
"url": "https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A9519"
},
{
"type": "WEB",
"url": "https://www.redhat.com/archives/fedora-package-announce/2008-May/msg00487.html"
},
{
"type": "WEB",
"url": "https://www.redhat.com/archives/fedora-package-announce/2008-May/msg00590.html"
},
{
"type": "WEB",
"url": "https://www.redhat.com/archives/fedora-package-announce/2008-May/msg00615.html"
},
{
"type": "WEB",
"url": "http://git.savannah.gnu.org/gitweb/?p=gnutls.git%3Ba=commitdiff%3Bh=bc8102405fda11ea00ca3b42acc4f4bce9d6e97b"
},
{
"type": "WEB",
"url": "http://git.savannah.gnu.org/gitweb/?p=gnutls.git;a=commitdiff;h=bc8102405fda11ea00ca3b42acc4f4bce9d6e97b"
},
{
"type": "WEB",
"url": "http://lists.gnu.org/archive/html/gnutls-devel/2008-05/msg00051.html"
},
{
"type": "WEB",
"url": "http://lists.gnu.org/archive/html/gnutls-devel/2008-05/msg00055.html"
},
{
"type": "WEB",
"url": "http://lists.gnu.org/archive/html/gnutls-devel/2008-05/msg00060.html"
},
{
"type": "WEB",
"url": "http://lists.opensuse.org/opensuse-security-announce/2008-09/msg00003.html"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/30287"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/30302"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/30317"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/30324"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/30330"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/30331"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/30338"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/30355"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/31939"
},
{
"type": "WEB",
"url": "http://security.gentoo.org/glsa/glsa-200805-20.xml"
},
{
"type": "WEB",
"url": "http://securityreason.com/securityalert/3902"
},
{
"type": "WEB",
"url": "http://sourceforge.net/project/shownotes.php?release_id=600646\u0026group_id=21558"
},
{
"type": "WEB",
"url": "http://wiki.rpath.com/wiki/Advisories:rPSA-2008-0174"
},
{
"type": "WEB",
"url": "http://www.cert.fi/haavoittuvuudet/advisory-gnutls.html"
},
{
"type": "WEB",
"url": "http://www.debian.org/security/2008/dsa-1581"
},
{
"type": "WEB",
"url": "http://www.kb.cert.org/vuls/id/252626"
},
{
"type": "WEB",
"url": "http://www.mandriva.com/security/advisories?name=MDVSA-2008:106"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2008/05/20/1"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2008/05/20/2"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2008/05/20/3"
},
{
"type": "WEB",
"url": "http://www.redhat.com/support/errata/RHSA-2008-0489.html"
},
{
"type": "WEB",
"url": "http://www.redhat.com/support/errata/RHSA-2008-0492.html"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/492282/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/492464/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/29292"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id?1020058"
},
{
"type": "WEB",
"url": "http://www.ubuntu.com/usn/usn-613-1"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2008/1582/references"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2008/1583/references"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-5MRQ-972X-QWR6
Vulnerability from github – Published: 2022-04-20 00:00 – Updated: 2025-05-05 18:31The SiteGround Security plugin for WordPress is vulnerable to authentication bypass that allows unauthenticated users to log in as administrative users due to missing identity verification on initial 2FA set-up that allows unauthenticated and unauthorized users to configure 2FA for pending accounts. Upon successful configuration, the attacker is logged in as that user without access to a username/password pair which is the expected first form of authentication. This affects versions up to, and including, 1.2.5.
{
"affected": [],
"aliases": [
"CVE-2022-0992"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-288",
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-04-19T21:15:00Z",
"severity": "CRITICAL"
},
"details": "The SiteGround Security plugin for WordPress is vulnerable to authentication bypass that allows unauthenticated users to log in as administrative users due to missing identity verification on initial 2FA set-up that allows unauthenticated and unauthorized users to configure 2FA for pending accounts. Upon successful configuration, the attacker is logged in as that user without access to a username/password pair which is the expected first form of authentication. This affects versions up to, and including, 1.2.5.",
"id": "GHSA-5mrq-972x-qwr6",
"modified": "2025-05-05T18:31:39Z",
"published": "2022-04-20T00:00:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-0992"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/2706302"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/blog/2022/04/critical-authentication-bypass-vulnerability-patched-in-siteground-security-plugin"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/6e5c6bf7-a653-4571-9566-574d2bb35c4f?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-5MWJ-V5JW-5C97
Vulnerability from github – Published: 2026-04-08 15:04 – Updated: 2026-04-09 14:28Summary
The webapi authentication layer trusts a client-controlled X-lobe-chat-auth header that is only XOR-obfuscated, not signed or otherwise authenticated. Because the XOR key is hardcoded in the repository, an attacker can forge arbitrary auth payloads and bypass authentication on protected webapi routes.
Affected routes include:
- POST /webapi/chat/[provider]
- GET /webapi/models/[provider]
- POST /webapi/models/[provider]/pull
- POST /webapi/create-image/comfyui
Details
The frontend creates X-lobe-chat-auth by XOR-obfuscating JSON with the static key LobeHub · LobeHub, and the backend reverses that operation and treats the decoded JSON as trusted authentication data.
The backend then accepts any truthy apiKey field in that decoded payload as sufficient authentication. No real API key validation is performed in this path.
As a result, an unauthenticated attacker can forge payloads such as:
{"apiKey":"x"}
or
{"userId":"victim-user-123","apiKey":"x"}
and access webapi routes as an authenticated user.
Confirmed PoC The following forged header was generated directly from the published XOR key using payload {"apiKey":"x"}:
X-lobe-chat-auth: N00DFSE+B1ngjQI0TR8=
That header decodes server-side to:
{"apiKey":"x"}
A simple request is:
curl 'https://TARGET/webapi/models/openai' \
-H 'X-lobe-chat-auth: N00DFSE+B1ngjQI0TR8='
If the deployment has OPENAI_API_KEY configured, the request should succeed without a real login and return the provider model list.
A forged impersonation payload also works conceptually:
{"userId":"victim-user-123","apiKey":"x"}
Impact
This is an unauthenticated authentication bypass.
An attacker can:
- access protected webapi routes without a valid session
- spend the deployment's server-side model provider credentials when env keys like OPENAI_API_KEY are configured
- impersonate another user's userId for routes that load per-user provider configuration
- invoke privileged backend model operations such as chat, model listing, model pulls, and ComfyUI image generation
Root Cause
The core issue is trusting unsigned client-supplied auth data:
- the auth header is only obfuscated, not authenticated
- the obfuscation key is hardcoded and recoverable from the repository
- the decoded apiKey field is treated as sufficient authentication even though it is never validated in this code path
- Suggested Remediation
- Stop treating X-lobe-chat-auth as an authentication token.
- Remove the apiKey truthiness check as an auth decision.
- Require a real server-validated session, OIDC token, or validated API key for all protected webapi routes.
- If a client payload is still needed, sign it server-side with an HMAC or replace it with a normal session-bound backend lookup.
- Affected Products
Ecosystem: npm
Package name: @lobehub/lobehub Affected versions: <= 2.1.47 Patched versions: 2.1.48
Severity Moderate Vector String CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
Weaknesses CWE-287: Improper Authentication CWE-345: Insufficient Verification of Data Authenticity CWE-290: Authentication Bypass by Spoofing
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 2.1.47"
},
"package": {
"ecosystem": "npm",
"name": "@lobehub/lobehub"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.1.48"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-39411"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-290",
"CWE-345"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-08T15:04:30Z",
"nvd_published_at": "2026-04-08T20:16:25Z",
"severity": "MODERATE"
},
"details": "# Summary\n\nThe `webapi` authentication layer trusts a client-controlled `X-lobe-chat-auth` header that is only XOR-obfuscated, not signed or otherwise authenticated. Because the XOR key is hardcoded in the repository, an attacker can forge arbitrary auth payloads and bypass authentication on protected `webapi` routes.\n\nAffected routes include:\n- `POST /webapi/chat/[provider]`\n- `GET /webapi/models/[provider]`\n- `POST /webapi/models/[provider]/pull`\n- `POST /webapi/create-image/comfyui`\n\n## Details\n\nThe frontend creates `X-lobe-chat-auth` by XOR-obfuscating JSON with the static key `LobeHub \u00b7 LobeHub`, and the backend reverses that operation and treats the decoded JSON as trusted authentication data.\n\nThe backend then accepts any truthy `apiKey` field in that decoded payload as sufficient authentication. No real API key validation is performed in this path.\n\nAs a result, an unauthenticated attacker can forge payloads such as:\n\n```json\n{\"apiKey\":\"x\"} \n```\n\nor \n\n``` {\"userId\":\"victim-user-123\",\"apiKey\":\"x\"} ```\n\nand access webapi routes as an authenticated user.\n\nConfirmed PoC\nThe following forged header was generated directly from the published XOR key using payload {\"apiKey\":\"x\"}:\n\n\n``` X-lobe-chat-auth: N00DFSE+B1ngjQI0TR8= ```\n\nThat header decodes server-side to:\n\n``` {\"apiKey\":\"x\"}```\n\nA simple request is:\n\n``` curl \u0027https://TARGET/webapi/models/openai\u0027 \\\n -H \u0027X-lobe-chat-auth: N00DFSE+B1ngjQI0TR8=\u0027 ``` \n\nIf the deployment has OPENAI_API_KEY configured, the request should succeed without a real login and return the provider model list.\n\nA forged impersonation payload also works conceptually:\n\n``` {\"userId\":\"victim-user-123\",\"apiKey\":\"x\"} ``` \n\n### Impact\nThis is an unauthenticated authentication bypass.\n\nAn attacker can:\n\n1. access protected webapi routes without a valid session\n2. spend the deployment\u0027s server-side model provider credentials when env keys like OPENAI_API_KEY are configured\n3. impersonate another user\u0027s userId for routes that load per-user provider configuration\n4. invoke privileged backend model operations such as chat, model listing, model pulls, and ComfyUI image generation\n\n### Root Cause\nThe core issue is trusting unsigned client-supplied auth data:\n\n1. the auth header is only obfuscated, not authenticated\n2. the obfuscation key is hardcoded and recoverable from the repository\n3. the decoded apiKey field is treated as sufficient authentication even though it is never validated in this code path\n4. Suggested Remediation\n5. Stop treating X-lobe-chat-auth as an authentication token.\n6. Remove the apiKey truthiness check as an auth decision.\n7. Require a real server-validated session, OIDC token, or validated API key for all protected webapi routes.\n8. If a client payload is still needed, sign it server-side with an HMAC or replace it with a normal session-bound backend lookup.\n9. Affected Products\n\nEcosystem: npm\n\nPackage name: @lobehub/lobehub\nAffected versions: \u003c= 2.1.47\nPatched versions: 2.1.48\n\nSeverity\nModerate\nVector String\nCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L\n\nWeaknesses\nCWE-287: Improper Authentication\nCWE-345: Insufficient Verification of Data Authenticity\nCWE-290: Authentication Bypass by Spoofing",
"id": "GHSA-5mwj-v5jw-5c97",
"modified": "2026-04-09T14:28:56Z",
"published": "2026-04-08T15:04:30Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/lobehub/lobehub/security/advisories/GHSA-5mwj-v5jw-5c97"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-39411"
},
{
"type": "WEB",
"url": "https://github.com/lobehub/lobehub/pull/13535"
},
{
"type": "WEB",
"url": "https://github.com/lobehub/lobehub/commit/3327b293d66c013f076cbc16cdbd05a61a3d0428"
},
{
"type": "PACKAGE",
"url": "https://github.com/lobehub/lobehub"
},
{
"type": "WEB",
"url": "https://github.com/lobehub/lobehub/releases/tag/v2.1.48"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
],
"summary": "LobeHub: Unauthenticated authentication bypass on `webapi` routes via forgeable `X-lobe-chat-auth` header"
}
GHSA-5P2M-H2QG-QCQ6
Vulnerability from github – Published: 2022-05-13 01:18 – Updated: 2022-05-13 01:18The OneClickSigninBubbleView::WindowClosing function in browser/ui/views/sync/one_click_signin_bubble_view.cc in Google Chrome before 32.0.1700.76 on Windows and before 32.0.1700.77 on Mac OS X and Linux allows attackers to trigger a sync with an arbitrary Google account by leveraging improper handling of the closing of an untrusted signin confirm dialog.
{
"affected": [],
"aliases": [
"CVE-2013-6643"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2014-01-16T12:17:00Z",
"severity": "HIGH"
},
"details": "The OneClickSigninBubbleView::WindowClosing function in browser/ui/views/sync/one_click_signin_bubble_view.cc in Google Chrome before 32.0.1700.76 on Windows and before 32.0.1700.77 on Mac OS X and Linux allows attackers to trigger a sync with an arbitrary Google account by leveraging improper handling of the closing of an untrusted signin confirm dialog.",
"id": "GHSA-5p2m-h2qg-qcq6",
"modified": "2022-05-13T01:18:03Z",
"published": "2022-05-13T01:18:03Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2013-6643"
},
{
"type": "WEB",
"url": "https://code.google.com/p/chromium/issues/detail?id=321940"
},
{
"type": "WEB",
"url": "https://src.chromium.org/viewvc/chrome?revision=237115\u0026view=revision"
},
{
"type": "WEB",
"url": "http://googlechromereleases.blogspot.com/2014/01/stable-channel-update.html"
},
{
"type": "WEB",
"url": "http://lists.opensuse.org/opensuse-security-announce/2014-02/msg00008.html"
},
{
"type": "WEB",
"url": "http://www.debian.org/security/2014/dsa-2862"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-5P42-9WW9-5P77
Vulnerability from github – Published: 2022-05-17 02:00 – Updated: 2022-05-17 02:00Frams's Fast File EXchange (F*EX, aka fex) 20100208, and possibly other versions before 20110610, allows remote attackers to bypass authentication and upload arbitrary files via a request that lacks an authentication ID.
{
"affected": [],
"aliases": [
"CVE-2011-1409"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2011-06-24T20:55:00Z",
"severity": "MODERATE"
},
"details": "Frams\u0027s Fast File EXchange (F*EX, aka fex) 20100208, and possibly other versions before 20110610, allows remote attackers to bypass authentication and upload arbitrary files via a request that lacks an authentication ID.",
"id": "GHSA-5p42-9ww9-5p77",
"modified": "2022-05-17T02:00:38Z",
"published": "2022-05-17T02:00:38Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2011-1409"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/68005"
},
{
"type": "WEB",
"url": "http://fex.rus.uni-stuttgart.de/fex.html"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/44940"
},
{
"type": "WEB",
"url": "http://www.debian.org/security/2011/dsa-2259"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/48239"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-5P59-4GFW-79Q6
Vulnerability from github – Published: 2025-04-28 12:30 – Updated: 2025-04-28 12:30A vulnerability, which was classified as critical, was found in 20120630 Novel-Plus up to 0e156c04b4b7ce0563bef6c97af4476fcda8f160. Affected is the function genCode of the file novel-admin/src/main/java/com/java2nb/common/controller/GeneratorController.java. The manipulation leads to missing authentication. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
{
"affected": [],
"aliases": [
"CVE-2025-4019"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-04-28T12:15:32Z",
"severity": "MODERATE"
},
"details": "A vulnerability, which was classified as critical, was found in 20120630 Novel-Plus up to 0e156c04b4b7ce0563bef6c97af4476fcda8f160. Affected is the function genCode of the file novel-admin/src/main/java/com/java2nb/common/controller/GeneratorController.java. The manipulation leads to missing authentication. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.",
"id": "GHSA-5p59-4gfw-79q6",
"modified": "2025-04-28T12:30:25Z",
"published": "2025-04-28T12:30:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-4019"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.306372"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.306372"
},
{
"type": "WEB",
"url": "https://vuldb.com/?submit.558360"
},
{
"type": "WEB",
"url": "https://www.cnblogs.com/aibot/p/18827469"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/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"
}
]
}
GHSA-5P5W-J3G7-W4WV
Vulnerability from github – Published: 2019-07-05 21:11 – Updated: 2021-06-11 14:24Versions of saml2-js prior to 1.12.4 or 2.0.2 are vulnerable to authentication bypass.
The saml2-js library may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.
Security Assertion Markup Language (SAML) is an XML-based markup language for security assertions regarding authentication and permissions, most commonly used for single sign-on (SSO) services.
Some XML DOM traversal and canonicalization APIs may be inconsistent in handling of comments within XML nodes. Incorrect use of these APIs by some SAML libraries results in incorrect parsing of the inner text of XML nodes such that any inner text after the comment is lost prior to cryptographically signing the SAML message. Text after the comment therefore has no impact on the signature on the SAML message.
A remote attacker can modify SAML content for a SAML service provider without invalidating the cryptographic signature, which may allow attackers to bypass primary authentication for the affected SAML service provider
Recommendation
If you use 1.x upgrade to version 1.12.4 or greater If you use 2.x upgrade to version 2.02 or greater
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "saml2-js"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.12.4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "saml2-js"
},
"ranges": [
{
"events": [
{
"introduced": "2.0.0"
},
{
"fixed": "2.0.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2017-11429"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": true,
"github_reviewed_at": "2020-06-16T21:16:53Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "Versions of `saml2-js` prior to 1.12.4 or 2.0.2 are vulnerable to authentication bypass.\n\nThe `saml2-js` library may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.\n\nSecurity Assertion Markup Language (SAML) is an XML-based markup language for security assertions regarding authentication and permissions, most commonly used for single sign-on (SSO) services.\n\nSome XML DOM traversal and canonicalization APIs may be inconsistent in handling of comments within XML nodes. Incorrect use of these APIs by some SAML libraries results in incorrect parsing of the inner text of XML nodes such that any inner text after the comment is lost prior to cryptographically signing the SAML message. Text after the comment therefore has no impact on the signature on the SAML message.\n\nA remote attacker can modify SAML content for a SAML service provider without invalidating the cryptographic signature, which may allow attackers to bypass primary authentication for the affected SAML service provider\n\n\n## Recommendation\n\nIf you use 1.x upgrade to version 1.12.4 or greater \nIf you use 2.x upgrade to version 2.02 or greater",
"id": "GHSA-5p5w-j3g7-w4wv",
"modified": "2021-06-11T14:24:18Z",
"published": "2019-07-05T21:11:18Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-11429"
},
{
"type": "WEB",
"url": "https://duo.com/blog/duo-finds-saml-vulnerabilities-affecting-multiple-implementations"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-5p5w-j3g7-w4wv"
},
{
"type": "WEB",
"url": "https://www.kb.cert.org/vuls/id/475445"
},
{
"type": "WEB",
"url": "https://www.npmjs.com/advisories/567"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Authentication bypass via incorrect XML canonicalization and DOM traversal in saml2-js"
}
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.