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.
5966 vulnerabilities reference this CWE, most recent first.
GHSA-MQVH-83G7-MC9G
Vulnerability from github – Published: 2022-05-14 03:29 – Updated: 2022-05-14 03:29The search and replay servers in IBM Tealeaf Customer Experience 8.0 through 9.0.2 allow remote attackers to bypass authentication via unspecified vectors. IBM X-Force ID: 105896.
{
"affected": [],
"aliases": [
"CVE-2015-4987"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-03-27T17:29:00Z",
"severity": "MODERATE"
},
"details": "The search and replay servers in IBM Tealeaf Customer Experience 8.0 through 9.0.2 allow remote attackers to bypass authentication via unspecified vectors. IBM X-Force ID: 105896.",
"id": "GHSA-mqvh-83g7-mc9g",
"modified": "2022-05-14T03:29:49Z",
"published": "2022-05-14T03:29:49Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2015-4987"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/105896"
},
{
"type": "WEB",
"url": "http://www-01.ibm.com/support/docview.wss?uid=swg21981017"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-MR2G-23MQ-VJ3H
Vulnerability from github – Published: 2022-09-20 00:00 – Updated: 2022-09-22 00:00A vulnerability in Trend Micro Apex One and Trend Micro Apex One as a Service could allow an attacker to bypass the product’s login authentication by falsifying request parameters on affected installations.
{
"affected": [],
"aliases": [
"CVE-2022-40144"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-09-19T18:15:00Z",
"severity": "CRITICAL"
},
"details": "A vulnerability in Trend Micro Apex One and Trend Micro Apex One as a Service could allow an attacker to bypass the product\u2019s login authentication by falsifying request parameters on affected installations.",
"id": "GHSA-mr2g-23mq-vj3h",
"modified": "2022-09-22T00:00:31Z",
"published": "2022-09-20T00:00:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-40144"
},
{
"type": "WEB",
"url": "https://appweb.trendmicro.com/SupportNews/NewsDetail.aspx?id=4553"
},
{
"type": "WEB",
"url": "https://jvn.jp/en/jp/JVN36454862/index.html"
},
{
"type": "WEB",
"url": "https://success.trendmicro.com/solution/000291528"
},
{
"type": "WEB",
"url": "https://www.ipa.go.jp/security/ciadr/vul/20220913-jvn.html"
}
],
"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-MR2R-XH4P-QMMP
Vulnerability from github – Published: 2022-05-17 00:38 – Updated: 2022-05-17 00:38TurnkeyForms Entertainment Portal 2.0 allows remote attackers to bypass authentication and gain administrative access by setting the adminLogged cookie to Administrator.
{
"affected": [],
"aliases": [
"CVE-2008-6723"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-04-14T16:26:00Z",
"severity": "HIGH"
},
"details": "TurnkeyForms Entertainment Portal 2.0 allows remote attackers to bypass authentication and gain administrative access by setting the adminLogged cookie to Administrator.",
"id": "GHSA-mr2r-xh4p-qmmp",
"modified": "2022-05-17T00:38:33Z",
"published": "2022-05-17T00:38:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-6723"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/46422"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/7028"
},
{
"type": "WEB",
"url": "http://osvdb.org/49749"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/32535"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/32174"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-MR33-RJV2-Q977
Vulnerability from github – Published: 2022-05-17 00:00 – Updated: 2022-05-26 00:01A remote authentication bypass vulnerability was discovered in Aruba ClearPass Policy Manager version(s): 6.10.4 and below, 6.9.9 and below, 6.8.9-HF2 and below, 6.7.x and below. Aruba has released updates to ClearPass Policy Manager that address this security vulnerability.
{
"affected": [],
"aliases": [
"CVE-2022-23660"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-05-16T20:15:00Z",
"severity": "CRITICAL"
},
"details": "A remote authentication bypass vulnerability was discovered in Aruba ClearPass Policy Manager version(s): 6.10.4 and below, 6.9.9 and below, 6.8.9-HF2 and below, 6.7.x and below. Aruba has released updates to ClearPass Policy Manager that address this security vulnerability.",
"id": "GHSA-mr33-rjv2-q977",
"modified": "2022-05-26T00:01:24Z",
"published": "2022-05-17T00:00:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-23660"
},
{
"type": "WEB",
"url": "https://www.arubanetworks.com/assets/alert/ARUBA-PSA-2022-007.txt"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-MR34-8733-GRR2
Vulnerability from github – Published: 2025-11-14 22:09 – Updated: 2026-03-12 11:00Summary
Access Tokens are used to authenticate application access. When a user changes their password, the existing list of Access Tokens stay valid instead of expiring. If a user finds that their account has been compromised, they can update their password.
The bad actor though will still have access to their account because the bad actor's Access Token stays on the list as a valid token. The user will have to manually delete the bad actor's Access Token to secure their account. The list of Access Tokens has a generic Description which makes it hard to pinpoint a bad actor in a list of Access Tokens.
Details
To improve Memos security, all Access Tokens will need to be revoked when a user changes their password. This removes the session for all the user's devices and prompts the user to log in again. You can treat the old Access Tokens as "invalid" because those Access Tokens were created with the older password.
PoC
- Have 2 devices on hand
- Log onto your Memos account on both devices. Notice how Access Tokens are created for each.
- On one device, successfully change the password. Refresh the page on the 2nd device and notice how it doesn't log out the user.
- On the 2nd device, change the password again. Refresh the page on the 1st device and notice how it doesn't log out the user.
Impact
A bad actor will still have access to the user's account because the Access Token does not expire on a password update. Having multi-factor authentication will vastly improve account security in Account Takeover cases instead of just relying on a password.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.18.1"
},
"package": {
"ecosystem": "Go",
"name": "github.com/usememos/memos"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.18.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-21635"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": true,
"github_reviewed_at": "2025-11-14T22:09:54Z",
"nvd_published_at": "2025-11-14T15:15:48Z",
"severity": "HIGH"
},
"details": "### Summary\nAccess Tokens are used to authenticate application access. When a user changes their password, the existing list of Access Tokens stay valid instead of expiring. If a user finds that their account has been compromised, they can update their password. \n\nThe bad actor though will still have access to their account because the bad actor\u0027s Access Token stays on the list as a valid token. The user will have to manually delete the bad actor\u0027s Access Token to secure their account. The list of Access Tokens has a generic Description which makes it hard to pinpoint a bad actor in a list of Access Tokens. \n\n### Details\n\nTo improve Memos security, all Access Tokens will need to be revoked when a user changes their password. This removes the session for all the user\u0027s devices and prompts the user to log in again. You can treat the old Access Tokens as \"invalid\" because those Access Tokens were created with the older password.\n\n### PoC\n\n1. Have 2 devices on hand\n2. Log onto your Memos account on both devices. Notice how Access Tokens are created for each.\n3. On one device, successfully change the password. Refresh the page on the 2nd device and notice how it doesn\u0027t log out the user.\n4. On the 2nd device, change the password again. Refresh the page on the 1st device and notice how it doesn\u0027t log out the user.\n\n### Impact\n\nA bad actor will still have access to the user\u0027s account because the Access Token does not expire on a password update. Having multi-factor authentication will vastly improve account security in Account Takeover cases instead of just relying on a password.",
"id": "GHSA-mr34-8733-grr2",
"modified": "2026-03-12T11:00:01Z",
"published": "2025-11-14T22:09:54Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/usememos/memos/security/advisories/GHSA-mr34-8733-grr2"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-21635"
},
{
"type": "PACKAGE",
"url": "https://github.com/usememos/memos"
},
{
"type": "WEB",
"url": "https://github.com/usememos/memos/releases/tag/v0.18.2"
},
{
"type": "WEB",
"url": "https://owasp.org/Top10/A04_2021-Insecure_Design"
},
{
"type": "WEB",
"url": "http://owasp.org/Top10/A07_2021-Identification_and_Authentication_Failures"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Memos\u0027 Access Tokens Stay Valid after User Password Change"
}
GHSA-MR82-9G27-QR4X
Vulnerability from github – Published: 2023-07-06 19:24 – Updated: 2024-04-04 05:35The listed versions of Nexx Smart Home devices could allow any user to register an already registered alarm or associated device with only the device’s MAC address.
{
"affected": [],
"aliases": [
"CVE-2023-1752"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-04-04T17:15:00Z",
"severity": "MODERATE"
},
"details": "The listed versions of Nexx Smart Home devices could allow any user to register an already registered alarm or associated device with only the device\u2019s MAC address.",
"id": "GHSA-mr82-9g27-qr4x",
"modified": "2024-04-04T05:35:35Z",
"published": "2023-07-06T19:24:13Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1752"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/news-events/ics-advisories/icsa-23-094-01"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-MR8H-J9CV-4M8H
Vulnerability from github – Published: 2021-04-22 16:11 – Updated: 2021-04-22 14:30Authentication.logout() helper in com.vaadin:flow-client versions 5.0.0 prior to 6.0.0 (Vaadin 18), and 6.0.0 through 6.0.4 (Vaadin 19.0.0 through 19.0.3) uses incorrect HTTP method, which, in combination with Spring Security CSRF protection, allows local attackers to access Fusion endpoints after the user attempted to log out.
- https://vaadin.com/security/cve-2021-31408
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "com.vaadin:vaadin-bom"
},
"ranges": [
{
"events": [
{
"introduced": "18.0.0"
},
{
"fixed": "19.0.4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-31408"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-613"
],
"github_reviewed": true,
"github_reviewed_at": "2021-04-22T14:30:10Z",
"nvd_published_at": "2021-04-23T17:15:00Z",
"severity": "MODERATE"
},
"details": "`Authentication.logout()` helper in `com.vaadin:flow-client` versions 5.0.0 prior to 6.0.0 (Vaadin 18), and 6.0.0 through 6.0.4 (Vaadin 19.0.0 through 19.0.3) uses incorrect HTTP method, which, in combination with Spring Security CSRF protection, allows local attackers to access Fusion endpoints after the user attempted to log out.\n\n- https://vaadin.com/security/cve-2021-31408",
"id": "GHSA-mr8h-j9cv-4m8h",
"modified": "2021-04-22T14:30:10Z",
"published": "2021-04-22T16:11:17Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/vaadin/platform/security/advisories/GHSA-mr8h-j9cv-4m8h"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-31408"
},
{
"type": "WEB",
"url": "https://github.com/vaadin/flow/pull/10577"
},
{
"type": "WEB",
"url": "https://vaadin.com/security/cve-2021-31408"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "Server session is not invalidated when logout() helper method of Authentication module is used in Vaadin 18-19"
}
GHSA-MR8Q-567W-34VP
Vulnerability from github – Published: 2022-05-02 06:15 – Updated: 2022-05-02 06:15The base-files package before 5.0.0ubuntu7.1 on Ubuntu 9.10 and before 5.0.0ubuntu20.10.04.2 on Ubuntu 10.04 LTS, as shipped on Dell Latitude 2110 netbooks, does not require authentication for package installation, which allows remote archive servers and man-in-the-middle attackers to execute arbitrary code via a crafted package.
{
"affected": [],
"aliases": [
"CVE-2010-0834"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2010-08-10T12:23:00Z",
"severity": "HIGH"
},
"details": "The base-files package before 5.0.0ubuntu7.1 on Ubuntu 9.10 and before 5.0.0ubuntu20.10.04.2 on Ubuntu 10.04 LTS, as shipped on Dell Latitude 2110 netbooks, does not require authentication for package installation, which allows remote archive servers and man-in-the-middle attackers to execute arbitrary code via a crafted package.",
"id": "GHSA-mr8q-567w-34vp",
"modified": "2022-05-02T06:15:58Z",
"published": "2022-05-02T06:15:58Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2010-0834"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/40889"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/42280"
},
{
"type": "WEB",
"url": "http://www.ubuntu.com/usn/usn-968-1"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2010/2015"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-MRFC-Q2C7-F9WW
Vulnerability from github – Published: 2022-05-13 00:01 – Updated: 2022-05-21 00:00Authentication Bypass Using an Alternate Path or Channel in GitHub repository requarks/wiki prior to 2.5.281. User can get root user permissions
{
"affected": [],
"aliases": [
"CVE-2022-1681"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-05-12T08:15:00Z",
"severity": "HIGH"
},
"details": "Authentication Bypass Using an Alternate Path or Channel in GitHub repository requarks/wiki prior to 2.5.281. User can get root user permissions",
"id": "GHSA-mrfc-q2c7-f9ww",
"modified": "2022-05-21T00:00:39Z",
"published": "2022-05-13T00:01:12Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-1681"
},
{
"type": "WEB",
"url": "https://github.com/requarks/wiki/commit/78d02dc8e5d103d248e5d7632bf7a6facdf4264c"
},
{
"type": "WEB",
"url": "https://huntr.dev/bounties/591b11e1-7504-4a96-99c6-08f2b419e767"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-MRGH-6X42-X6XF
Vulnerability from github – Published: 2022-05-17 05:13 – Updated: 2022-07-13 15:56The default configuration for Apache Qpid 0.20 and earlier, when the federation_tag attribute is enabled, accepts AMQP connections without checking the source user ID, which allows remote attackers to bypass authentication and have other unspecified impact via an AMQP request.
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.qpid:qpid-client"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.20"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2012-4446"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": true,
"github_reviewed_at": "2022-07-13T15:56:19Z",
"nvd_published_at": "2013-03-14T03:10:00Z",
"severity": "MODERATE"
},
"details": "The default configuration for Apache Qpid 0.20 and earlier, when the federation_tag attribute is enabled, accepts AMQP connections without checking the source user ID, which allows remote attackers to bypass authentication and have other unspecified impact via an AMQP request.",
"id": "GHSA-mrgh-6x42-x6xf",
"modified": "2022-07-13T15:56:19Z",
"published": "2022-05-17T05:13:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2012-4446"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=851355"
},
{
"type": "WEB",
"url": "https://issues.apache.org/jira/browse/QPID-4631"
},
{
"type": "WEB",
"url": "http://rhn.redhat.com/errata/RHSA-2013-0561.html"
},
{
"type": "WEB",
"url": "http://rhn.redhat.com/errata/RHSA-2013-0562.html"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "Improper Authentication in Apache Qpid"
}
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.