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.
5964 vulnerabilities reference this CWE, most recent first.
GHSA-V593-864P-WP43
Vulnerability from github – Published: 2022-11-11 19:00 – Updated: 2022-11-17 21:30Improper authentication in subsystem for Intel(R) AMT before versions 11.8.93, 11.22.93, 11.12.93, 12.0.92, 14.1.67, 15.0.42, 16.1.25 may allow a privileged user to potentially enable escalation of privilege via local access.
{
"affected": [],
"aliases": [
"CVE-2021-33159"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-11-11T16:15:00Z",
"severity": "MODERATE"
},
"details": "Improper authentication in subsystem for Intel(R) AMT before versions 11.8.93, 11.22.93, 11.12.93, 12.0.92, 14.1.67, 15.0.42, 16.1.25 may allow a privileged user to potentially enable escalation of privilege via local access.",
"id": "GHSA-v593-864p-wp43",
"modified": "2022-11-17T21:30:49Z",
"published": "2022-11-11T19:00:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-33159"
},
{
"type": "WEB",
"url": "https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00610.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-V5CP-96CW-FP58
Vulnerability from github – Published: 2022-05-17 01:44 – Updated: 2022-05-17 01:44The Java servlets in the management console in IBM Tivoli Federated Identity Manager (TFIM) through 6.2.2 and Tivoli Federated Identity Manager Business Gateway (TFIMBG) before 6.2.2 do not require authentication for all resource downloads, which allows remote attackers to bypass intended J2EE security constraints, and obtain sensitive information related to (1) federation metadata or (2) a web plugin configuration template, via a crafted request.
{
"affected": [],
"aliases": [
"CVE-2012-3315"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2012-11-08T11:46:00Z",
"severity": "MODERATE"
},
"details": "The Java servlets in the management console in IBM Tivoli Federated Identity Manager (TFIM) through 6.2.2 and Tivoli Federated Identity Manager Business Gateway (TFIMBG) before 6.2.2 do not require authentication for all resource downloads, which allows remote attackers to bypass intended J2EE security constraints, and obtain sensitive information related to (1) federation metadata or (2) a web plugin configuration template, via a crafted request.",
"id": "GHSA-v5cp-96cw-fp58",
"modified": "2022-05-17T01:44:29Z",
"published": "2022-05-17T01:44:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2012-3315"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/77796"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/51163"
},
{
"type": "WEB",
"url": "http://www-01.ibm.com/support/docview.wss?uid=swg1IV26825"
},
{
"type": "WEB",
"url": "http://www-01.ibm.com/support/docview.wss?uid=swg1IV26826"
},
{
"type": "WEB",
"url": "http://www-01.ibm.com/support/docview.wss?uid=swg1IV26827"
},
{
"type": "WEB",
"url": "http://www-01.ibm.com/support/docview.wss?uid=swg21615770"
},
{
"type": "WEB",
"url": "http://www-01.ibm.com/support/docview.wss?uid=swg21615772"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-V5FF-XR5W-X98P
Vulnerability from github – Published: 2022-05-14 01:36 – Updated: 2022-05-14 01:36WebAccess/SCADA, Version 8.3. Specially crafted requests could allow a possible authentication bypass that could allow an attacker to obtain and manipulate sensitive information.
{
"affected": [],
"aliases": [
"CVE-2019-6521"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-02-05T21:29:00Z",
"severity": "HIGH"
},
"details": "WebAccess/SCADA, Version 8.3. Specially crafted requests could allow a possible authentication bypass that could allow an attacker to obtain and manipulate sensitive information.",
"id": "GHSA-v5ff-xr5w-x98p",
"modified": "2022-05-14T01:36:19Z",
"published": "2022-05-14T01:36:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-6521"
},
{
"type": "WEB",
"url": "https://ics-cert.us-cert.gov/advisories/ICSA-19-024-01"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/106722"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-V5H3-WX8W-WPMX
Vulnerability from github – Published: 2023-11-15 15:30 – Updated: 2023-11-15 15:30Improper Authentication vulnerabiity in Samsung Pass prior to version 4.3.00.17 allows physical attackers to bypass authentication.
{
"affected": [],
"aliases": [
"CVE-2023-42554"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-11-07T08:15:23Z",
"severity": "MODERATE"
},
"details": "Improper Authentication vulnerabiity in Samsung Pass prior to version 4.3.00.17 allows physical attackers to bypass authentication.",
"id": "GHSA-v5h3-wx8w-wpmx",
"modified": "2023-11-15T15:30:20Z",
"published": "2023-11-15T15:30:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-42554"
},
{
"type": "WEB",
"url": "https://security.samsungmobile.com/serviceWeb.smsb?year=2023\u0026month=11"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-V5H6-RMJ4-6H5M
Vulnerability from github – Published: 2022-05-24 17:13 – Updated: 2022-05-24 17:13A vulnerability in Juniper Networks SRX Series device configured as a Junos OS Enforcer device may allow a user to access network resources that are not permitted by a UAC policy. This issue might occur when the IP address range configured in the Infranet Controller (IC) is configured as an IP address range instead of an IP address/netmask. See the Workaround section for more detail. The Junos OS Enforcer CLI settings are disabled by default. This issue affects Juniper Networks Junos OS on SRX Series: 12.3X48 versions prior to 12.3X48-D100; 15.1X49 versions prior to 15.1X49-D210; 17.3 versions prior to 17.3R2-S5, 17.3R3-S8; 17.4 versions prior to 17.4R2-S9, 17.4R3-S1; 18.1 versions prior to 18.1R3-S10; 18.2 versions prior to 18.2R2-S7, 18.2R3-S3; 18.3 versions prior to 18.3R1-S7, 18.3R3-S2; 18.4 versions prior to 18.4R1-S6, 18.4R2-S4, 18.4R3-S1; 19.1 versions prior to 19.1R1-S4, 19.1R2-S1, 19.1R3; 19.2 versions prior to 19.2R1-S3, 19.2R2; 19.3 versions prior to 19.3R2-S1, 19.3R3; 19.4 versions prior to 19.4R1-S1, 19.4R2.
{
"affected": [],
"aliases": [
"CVE-2020-1637"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-04-08T20:15:00Z",
"severity": "MODERATE"
},
"details": "A vulnerability in Juniper Networks SRX Series device configured as a Junos OS Enforcer device may allow a user to access network resources that are not permitted by a UAC policy. This issue might occur when the IP address range configured in the Infranet Controller (IC) is configured as an IP address range instead of an IP address/netmask. See the Workaround section for more detail. The Junos OS Enforcer CLI settings are disabled by default. This issue affects Juniper Networks Junos OS on SRX Series: 12.3X48 versions prior to 12.3X48-D100; 15.1X49 versions prior to 15.1X49-D210; 17.3 versions prior to 17.3R2-S5, 17.3R3-S8; 17.4 versions prior to 17.4R2-S9, 17.4R3-S1; 18.1 versions prior to 18.1R3-S10; 18.2 versions prior to 18.2R2-S7, 18.2R3-S3; 18.3 versions prior to 18.3R1-S7, 18.3R3-S2; 18.4 versions prior to 18.4R1-S6, 18.4R2-S4, 18.4R3-S1; 19.1 versions prior to 19.1R1-S4, 19.1R2-S1, 19.1R3; 19.2 versions prior to 19.2R1-S3, 19.2R2; 19.3 versions prior to 19.3R2-S1, 19.3R3; 19.4 versions prior to 19.4R1-S1, 19.4R2.",
"id": "GHSA-v5h6-rmj4-6h5m",
"modified": "2022-05-24T17:13:52Z",
"published": "2022-05-24T17:13:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-1637"
},
{
"type": "WEB",
"url": "https://kb.juniper.net/JSA11018"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-V5JW-8PJP-RGFP
Vulnerability from github – Published: 2022-03-11 00:02 – Updated: 2022-03-17 00:01TP-Link Omada SDN Software Controller before 5.0.15 does not check if the authentication method specified in a connection request is allowed. An attacker can bypass the captive portal authentication process by using the downgraded "no authentication" method, and access the protected network. For example, the attacker can simply set window.authType=0 in client-side JavaScript.
{
"affected": [],
"aliases": [
"CVE-2021-44032"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-03-10T17:44:00Z",
"severity": "HIGH"
},
"details": "TP-Link Omada SDN Software Controller before 5.0.15 does not check if the authentication method specified in a connection request is allowed. An attacker can bypass the captive portal authentication process by using the downgraded \"no authentication\" method, and access the protected network. For example, the attacker can simply set window.authType=0 in client-side JavaScript.",
"id": "GHSA-v5jw-8pjp-rgfp",
"modified": "2022-03-17T00:01:45Z",
"published": "2022-03-11T00:02:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-44032"
},
{
"type": "WEB",
"url": "https://github.com/Orange-Cyberdefense/CVE-repository/blob/master/PoCs/POC_CVE-2021-44032_Kevin.md"
},
{
"type": "WEB",
"url": "https://www.tp-link.com/us/omada-sdn"
},
{
"type": "WEB",
"url": "https://www.tp-link.com/us/security"
}
],
"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-V5PP-MXMW-5HVR
Vulnerability from github – Published: 2022-05-01 23:32 – Updated: 2022-05-01 23:32Unspecified vulnerability in the BIOS F.26 and earlier for the HP Compaq Notebook PC allows physically proximate attackers to obtain privileged access via unspecified vectors, possibly involving an authentication bypass of the power-on password.
{
"affected": [],
"aliases": [
"CVE-2008-0706"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2008-03-31T23:44:00Z",
"severity": "HIGH"
},
"details": "Unspecified vulnerability in the BIOS F.26 and earlier for the HP Compaq Notebook PC allows physically proximate attackers to obtain privileged access via unspecified vectors, possibly involving an authentication bypass of the power-on password.",
"id": "GHSA-v5pp-mxmw-5hvr",
"modified": "2022-05-01T23:32:34Z",
"published": "2022-05-01T23:32:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-0706"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/41521"
},
{
"type": "WEB",
"url": "http://marc.info/?l=bugtraq\u0026m=120672270224094\u0026w=2"
},
{
"type": "WEB",
"url": "http://securitytracker.com/id?1019730"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/28495"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2008/1043/references"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-V5QW-PP2P-CVPR
Vulnerability from github – Published: 2022-05-14 03:35 – Updated: 2022-05-14 03:35memcached before 1.4.17 allows remote attackers to bypass authentication by sending an invalid request with SASL credentials, then sending another request with incorrect SASL credentials.
{
"affected": [],
"aliases": [
"CVE-2013-7239"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2014-01-13T21:55:00Z",
"severity": "MODERATE"
},
"details": "memcached before 1.4.17 allows remote attackers to bypass authentication by sending an invalid request with SASL credentials, then sending another request with incorrect SASL credentials.",
"id": "GHSA-v5qw-pp2p-cvpr",
"modified": "2022-05-14T03:35:51Z",
"published": "2022-05-14T03:35:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2013-7239"
},
{
"type": "WEB",
"url": "https://code.google.com/p/memcached/wiki/ReleaseNotes1417"
},
{
"type": "WEB",
"url": "http://seclists.org/oss-sec/2013/q4/572"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/56183"
},
{
"type": "WEB",
"url": "http://www.debian.org/security/2014/dsa-2832"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/64559"
},
{
"type": "WEB",
"url": "http://www.ubuntu.com/usn/USN-2080-1"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-V5W9-PRXF-W882
Vulnerability from github – Published: 2025-11-17 19:06 – Updated: 2025-11-17 19:06Summary
An unauthenticated attacker can exploit the unprotected registration endpoint (/register) to create a new user and bypass authentication.
Details
Critical vulnerability in Flowise 3.0.1 on-premise deployment allows unauthenticated attackers to exploit the /api/v1/account/register endpoint to add a new user and log in using it, enabling authentication bypass.
Meaning that the register functionality is by default open, allowing attackers to create an account and use the api without any restrictions or credentials.
PoC
A Flowise 3.0.1 instance was deployed via Docker for the purpose of this demonstration.
After successful deployment the instance setup organization page allows us to register the first account in the system.
Creating the first user research@evasec.io
Login to the account
The background request that created the first user to /api/v1/account/register
Response
We have found that it is possible to reuse the registration request multiple times without any restrictions to create an account and authenticate to the system using it.
Crafting a new request
{
"user": {
"name": "Malicious",
"email": "attacker@attack.io",
"type": "pro",
"credential": "Password123!"
}
}
Response with 201 code “Created”
Login using newly created user (attacker)
Success login
An unauthorized user can exploit this vulnerability to register an account and gain access to the Flowise API with authenticated privileges, effectively bypassing authentication.
Impact
This is an authentication bypass vulnerability caused by an unprotected registration endpoint (/register).
Users of Flowise 3.0.1(latest) on-premise deployments are impacted. An unauthorized attacker can exploit this vulnerability to register an account after the organization set has been completed, and gain access to the Flowise API with authenticated privileges, effectively bypassing authentication.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "flowise"
},
"versions": [
"3.0.1"
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": true,
"github_reviewed_at": "2025-11-17T19:06:09Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "### Summary\nAn unauthenticated attacker can exploit the unprotected registration endpoint (/register) to create a new user and bypass authentication.\n### Details\nCritical vulnerability in Flowise 3.0.1 on-premise deployment allows unauthenticated attackers to exploit the /api/v1/account/register endpoint to add a new user and log in using it, enabling authentication bypass.\n\nMeaning that the register functionality is by default open, allowing attackers to create an account and use the api without any restrictions or credentials.\n\n### PoC\nA Flowise 3.0.1 instance was deployed via Docker for the purpose of this demonstration.\n\n\nAfter successful deployment the instance setup organization page allows us to register the first account in the system.\n\n\nCreating the first user [research@evasec.io](mailto:research@evasec.io)\n\n\nLogin to the account\n\n\nThe background request that created the first user to /api/v1/account/register \n\n\nResponse\n\n\nWe have found that it is possible to reuse the registration request multiple times without any restrictions to create an account and authenticate to the system using it.\n\nCrafting a new request \n{\n \"user\": {\n \"name\": \"Malicious\",\n \"email\": \"attacker@attack.io\", \n \"type\": \"pro\",\n \"credential\": \"Password123!\"\n }\n}\n\n\nResponse with 201 code \u201cCreated\u201d\n\n\nLogin using newly created user (attacker)\n\n\nSuccess login\n\n\n\nAn unauthorized user can exploit this vulnerability to register an account and gain access to the Flowise API with authenticated privileges, effectively bypassing authentication. \n### Impact\n\nThis is an authentication bypass vulnerability caused by an unprotected registration endpoint (/register).\n\nUsers of Flowise 3.0.1(latest) on-premise deployments are impacted. An unauthorized attacker can exploit this vulnerability to register an account after the organization set has been completed, and gain access to the Flowise API with authenticated privileges, effectively bypassing authentication.",
"id": "GHSA-v5w9-prxf-w882",
"modified": "2025-11-17T19:06:09Z",
"published": "2025-11-17T19:06:09Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-v5w9-prxf-w882"
},
{
"type": "PACKAGE",
"url": "https://github.com/FlowiseAI/Flowise"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Flowise has Authentication Bypass Using Unprotected Registration Endpoint (/register)"
}
GHSA-V5XM-MRQQ-93P7
Vulnerability from github – Published: 2022-05-13 01:26 – Updated: 2022-05-13 01:26Zimbra Collaboration Suite (ZCS) 6.0.16 and earlier allows man-in-the-middle attackers to obtain access by sniffing the network and replaying the ZM_AUTH_TOKEN token.
{
"affected": [],
"aliases": [
"CVE-2013-5119"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2013-09-23T20:55:00Z",
"severity": "MODERATE"
},
"details": "Zimbra Collaboration Suite (ZCS) 6.0.16 and earlier allows man-in-the-middle attackers to obtain access by sniffing the network and replaying the ZM_AUTH_TOKEN token.",
"id": "GHSA-v5xm-mrqq-93p7",
"modified": "2022-05-13T01:26:04Z",
"published": "2022-05-13T01:26:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2013-5119"
},
{
"type": "WEB",
"url": "http://archives.neohapsis.com/archives/bugtraq/2013-09/0063.html"
},
{
"type": "WEB",
"url": "http://osvdb.org/97290"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/62407"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.