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-VPXF-Q44G-W34W
Vulnerability from github – Published: 2023-06-30 20:36 – Updated: 2023-07-03 18:38Summary
There is a permission flaw in the Sealos billing system, which allows users to control the recharge resource account. sealos. io/v1/Payment, resulting in the ability to recharge any amount of 1 RMB.
Details
The reason is that sealos is in arrears. Egg pain, we can't create a terminal anymore. Let's charge for it:
Then it was discovered that the charging interface had returned all resource information. Unfortunately, based on previous vulnerability experience, the namespace of this custom resource is still under the current user's control and may have permission to correct it.
PoC
disable by publish
Impact
- sealos public cloud user
- CWE-287 Improper Authentication
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/labring/sealos"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "4.2.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2023-36815"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2023-06-30T20:36:55Z",
"nvd_published_at": "2023-07-03T18:15:09Z",
"severity": "HIGH"
},
"details": "### Summary\n\nThere is a permission flaw in the Sealos billing system, which allows users to control the recharge resource account. sealos. io/v1/Payment, resulting in the ability to recharge any amount of 1 RMB.\n\n### Details\n\nThe reason is that sealos is in arrears. Egg pain, we can\u0027t create a terminal anymore. Let\u0027s charge for it:\n\nThen it was discovered that the charging interface had returned all resource information. Unfortunately, based on previous vulnerability experience, the namespace of this custom resource is still under the current user\u0027s control and may have permission to correct it.\n\n### PoC\ndisable by publish\n\n### Impact\n\n+ sealos public cloud user\n+ CWE-287 Improper Authentication",
"id": "GHSA-vpxf-q44g-w34w",
"modified": "2023-07-03T18:38:23Z",
"published": "2023-06-30T20:36:55Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/labring/sealos/security/advisories/GHSA-vpxf-q44g-w34w"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-36815"
},
{
"type": "PACKAGE",
"url": "https://github.com/labring/sealos"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "Sealos billing system permission control defect"
}
GHSA-VQ34-7C65-CHV9
Vulnerability from github – Published: 2022-01-04 00:00 – Updated: 2022-01-08 00:00The server-request receiver function of Shockwall system has an improper authentication vulnerability. An authenticated attacker of an agent computer within the local area network can use the local registry information to launch server-side request forgery (SSRF) attack on another agent computer, resulting in arbitrary code execution for controlling the system or disrupting service.
{
"affected": [],
"aliases": [
"CVE-2021-45917"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-01-03T10:15:00Z",
"severity": "CRITICAL"
},
"details": "The server-request receiver function of Shockwall system has an improper authentication vulnerability. An authenticated attacker of an agent computer within the local area network can use the local registry information to launch server-side request forgery (SSRF) attack on another agent computer, resulting in arbitrary code execution for controlling the system or disrupting service.",
"id": "GHSA-vq34-7c65-chv9",
"modified": "2022-01-08T00:00:24Z",
"published": "2022-01-04T00:00:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-45917"
},
{
"type": "WEB",
"url": "https://www.twcert.org.tw/tw/cp-132-5433-77f6f-1.html"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-VQ34-C5HG-7R26
Vulnerability from github – Published: 2022-05-17 04:56 – Updated: 2022-05-17 04:56The user.login function in Zabbix before 1.8.16 and 2.x before 2.0.5rc1 allows remote attackers to override LDAP configuration via the cnf parameter.
{
"affected": [],
"aliases": [
"CVE-2013-1364"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2013-12-14T17:21:00Z",
"severity": "MODERATE"
},
"details": "The user.login function in Zabbix before 1.8.16 and 2.x before 2.0.5rc1 allows remote attackers to override LDAP configuration via the cnf parameter.",
"id": "GHSA-vq34-c5hg-7r26",
"modified": "2022-05-17T04:56:19Z",
"published": "2022-05-17T04:56:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2013-1364"
},
{
"type": "WEB",
"url": "https://support.zabbix.com/browse/ZBX-6097"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/55824"
},
{
"type": "WEB",
"url": "http://security.gentoo.org/glsa/glsa-201311-15.xml"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/57471"
},
{
"type": "WEB",
"url": "http://www.zabbix.com/rn1.8.16.php"
},
{
"type": "WEB",
"url": "http://www.zabbix.com/rn2.0.5rc1.php"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-VQ3Q-W9WV-XC6J
Vulnerability from github – Published: 2026-08-16 06:30 – Updated: 2026-08-17 21:31The Simple JWT Login WordPress plugin before 3.6.8 does not validate the audience of the Google identity tokens it accepts, allowing unauthenticated users to authenticate as any user whose email address such a token carries, up to and including an administrator. Every site with the Simple JWT Login WordPress plugin before 3.6.8's Google sign-in enabled is affected.
{
"affected": [],
"aliases": [
"CVE-2026-19714"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-16T06:16:52Z",
"severity": "CRITICAL"
},
"details": "The Simple JWT Login WordPress plugin before 3.6.8 does not validate the audience of the Google identity tokens it accepts, allowing unauthenticated users to authenticate as any user whose email address such a token carries, up to and including an administrator. Every site with the Simple JWT Login WordPress plugin before 3.6.8\u0027s Google sign-in enabled is affected.",
"id": "GHSA-vq3q-w9wv-xc6j",
"modified": "2026-08-17T21:31:18Z",
"published": "2026-08-16T06:30:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-19714"
},
{
"type": "WEB",
"url": "https://wpscan.com/vulnerability/dc6e54eb-d856-484b-88c1-b3e04a37669d"
}
],
"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:N",
"type": "CVSS_V3"
}
]
}
GHSA-VQ42-25HH-C536
Vulnerability from github – Published: 2022-05-02 03:40 – Updated: 2022-05-02 03:40** DISPUTED ** The Command Line Interface (aka Server CLI or administration interface) in the master process in the reverse proxy server in Varnish before 2.1.0 does not require authentication for commands received through a TCP port, which allows remote attackers to (1) execute arbitrary code via a vcl.inline directive that provides a VCL configuration file containing inline C code; (2) change the ownership of the master process via param.set, stop, and start directives; (3) read the initial line of an arbitrary file via a vcl.load directive; or (4) conduct cross-site request forgery (CSRF) attacks that leverage a victim's location on a trusted network and improper input validation of directives. NOTE: the vendor disputes this report, saying that it is "fundamentally misguided and pointless."
{
"affected": [],
"aliases": [
"CVE-2009-2936"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2010-04-05T16:30:00Z",
"severity": "HIGH"
},
"details": "** DISPUTED ** The Command Line Interface (aka Server CLI or administration interface) in the master process in the reverse proxy server in Varnish before 2.1.0 does not require authentication for commands received through a TCP port, which allows remote attackers to (1) execute arbitrary code via a vcl.inline directive that provides a VCL configuration file containing inline C code; (2) change the ownership of the master process via param.set, stop, and start directives; (3) read the initial line of an arbitrary file via a vcl.load directive; or (4) conduct cross-site request forgery (CSRF) attacks that leverage a victim\u0027s location on a trusted network and improper input validation of directives. NOTE: the vendor disputes this report, saying that it is \"fundamentally misguided and pointless.\"",
"id": "GHSA-vq42-25hh-c536",
"modified": "2022-05-02T03:40:08Z",
"published": "2022-05-02T03:40:08Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2009-2936"
},
{
"type": "WEB",
"url": "http://lists.fedoraproject.org/pipermail/package-announce/2010-April/040359.html"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/510360/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/510368/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.varnish-cache.org/changeset/3865"
},
{
"type": "WEB",
"url": "http://www.varnish-cache.org/wiki/CLI"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-VQ53-8C3W-P2FR
Vulnerability from github – Published: 2023-11-30 18:31 – Updated: 2023-11-30 18:31Tyler Technologies Magistrate Court Case Management Plus allows an unauthenticated, remote attacker to upload, delete, and view files by manipulating the PDFViewer.aspx 'filename' parameter.
{
"affected": [],
"aliases": [
"CVE-2023-6354"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-11-30T18:15:09Z",
"severity": "MODERATE"
},
"details": "Tyler Technologies Magistrate Court Case Management Plus allows an unauthenticated, remote attacker to upload, delete, and view files by manipulating the PDFViewer.aspx \u0027filename\u0027 parameter.\n\n\n",
"id": "GHSA-vq53-8c3w-p2fr",
"modified": "2023-11-30T18:31:19Z",
"published": "2023-11-30T18:31:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-6354"
},
{
"type": "WEB",
"url": "https://github.com/qwell/disorder-in-the-court/blob/main/README-TylerTechnologies.md"
},
{
"type": "WEB",
"url": "https://techcrunch.com/2023/11/30/us-court-records-systems-vulnerabilities-exposed-sealed-documents"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/news-events/alerts/2023/11/30/multiple-vulnerabilities-affecting-web-based-court-case-and-document-management-systems"
},
{
"type": "WEB",
"url": "https://www.tylertech.com/solutions/courts-public-safety/courts-justice"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-VQ5P-MC3M-CRGG
Vulnerability from github – Published: 2022-05-17 00:34 – Updated: 2022-05-17 00:34The Simple Student Result plugin before 1.6.4 for WordPress has an Authentication Bypass vulnerability because the fn_ssr_add_st_submit() function and fn_ssr_del_st_submit() function in functions.php only require knowing the student id number.
{
"affected": [],
"aliases": [
"CVE-2017-14766"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-09-27T08:29:00Z",
"severity": "HIGH"
},
"details": "The Simple Student Result plugin before 1.6.4 for WordPress has an Authentication Bypass vulnerability because the fn_ssr_add_st_submit() function and fn_ssr_del_st_submit() function in functions.php only require knowing the student id number.",
"id": "GHSA-vq5p-mc3m-crgg",
"modified": "2022-05-17T00:34:23Z",
"published": "2022-05-17T00:34:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-14766"
},
{
"type": "WEB",
"url": "https://limbenjamin.com/articles/simple-student-result-auth-bypass.html"
},
{
"type": "WEB",
"url": "https://wordpress.org/plugins/simple-student-result/#developers"
},
{
"type": "WEB",
"url": "https://wpvulndb.com/vulnerabilities/8920"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-VQ65-25J7-7M98
Vulnerability from github – Published: 2022-05-17 00:41 – Updated: 2022-05-17 00:41OwenPoll 1.0 allows remote attackers to bypass authentication and obtain administrative access via a modified account name in the username cookie.
{
"affected": [],
"aliases": [
"CVE-2008-6143"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-02-16T17:30:00Z",
"severity": "HIGH"
},
"details": "OwenPoll 1.0 allows remote attackers to bypass authentication and obtain administrative access via a modified account name in the username cookie.",
"id": "GHSA-vq65-25j7-7m98",
"modified": "2022-05-17T00:41:13Z",
"published": "2022-05-17T00:41:13Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-6143"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/7597"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/33032"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-VQ6G-G6C7-5F2J
Vulnerability from github – Published: 2026-09-24 19:54 – Updated: 2026-09-24 19:54Impact
The SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued AuthnRequest.
Applications using SAML account association could allow an attacker with a valid account on a trusted IdP to link the attacker's SAML identity to a logged-in victim's local account. The attacker could then authenticate through SAML and gain access to the victim's account.
The issue affects applications using the SAML backend together with authenticated account association.
Patches
The issue has been fixed by validating SAML responses against stored AuthnRequest IDs.
Users should upgrade to a patched version.
Fix:
- https://github.com/python-social-auth/social-core/pull/1794
Workarounds
Applications that cannot upgrade immediately should disable SAML account association for already authenticated users.
If SAML login is not required, the SAML backend can also be disabled by removing it from SOCIAL_AUTH_AUTHENTICATION_BACKENDS.
There is no complete workaround while continuing to allow vulnerable SAML account association.
Credits
Reported through GitHub private vulnerability reporting by Liyi Zhou, Ziyue Wang, Strick, Maurice, and Chenchen Yu from the University of Sydney security research team.
Reporter references:
- https://lzhou1110.github.io/
- https://zyy0530.github.io/
- https://str1ckl4nd.github.io/
- https://maurice.busystar.org/
- https://7thparkk.github.io/
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "social-auth-core"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.0.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-57175"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": true,
"github_reviewed_at": "2026-09-24T19:54:48Z",
"nvd_published_at": "2026-09-24T18:17:14Z",
"severity": "MODERATE"
},
"details": "### Impact\n\nThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued `AuthnRequest`.\n\nApplications using SAML account association could allow an attacker with a valid account on a trusted IdP to link the attacker\u0027s SAML identity to a logged-in victim\u0027s local account. The attacker could then authenticate through SAML and gain access to the victim\u0027s account.\n\nThe issue affects applications using the SAML backend together with authenticated account association.\n\n### Patches\n\nThe issue has been fixed by validating SAML responses against stored `AuthnRequest` IDs.\n\nUsers should upgrade to a patched version.\n\nFix:\n\n* https://github.com/python-social-auth/social-core/pull/1794\n\n### Workarounds\n\nApplications that cannot upgrade immediately should disable SAML account association for already authenticated users.\n\nIf SAML login is not required, the SAML backend can also be disabled by removing it from `SOCIAL_AUTH_AUTHENTICATION_BACKENDS`.\n\nThere is no complete workaround while continuing to allow vulnerable SAML account association.\n\n### Credits\n\nReported through GitHub private vulnerability reporting by Liyi Zhou, Ziyue Wang, Strick, Maurice, and Chenchen Yu from the University of Sydney security research team.\n\nReporter references:\n\n* https://lzhou1110.github.io/\n* https://zyy0530.github.io/\n* https://str1ckl4nd.github.io/\n* https://maurice.busystar.org/\n* https://7thparkk.github.io/",
"id": "GHSA-vq6g-g6c7-5f2j",
"modified": "2026-09-24T19:54:48Z",
"published": "2026-09-24T19:54:48Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/python-social-auth/social-core/security/advisories/GHSA-vq6g-g6c7-5f2j"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-57175"
},
{
"type": "WEB",
"url": "https://github.com/python-social-auth/social-core/pull/1794"
},
{
"type": "WEB",
"url": "https://github.com/python-social-auth/social-core/commit/5c72f71125bc60e4411f09e2a9f998de5da7fcb6"
},
{
"type": "PACKAGE",
"url": "https://github.com/python-social-auth/social-core"
},
{
"type": "WEB",
"url": "https://github.com/python-social-auth/social-core/releases/tag/5.0.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "social-auth-core has an Improper Authentication issue"
}
GHSA-VQ6X-7G8M-7QHJ
Vulnerability from github – Published: 2026-09-08 21:34 – Updated: 2026-09-08 21:34A vulnerability was detected in Open-Web-Analytics up to 1.9.1. The impacted element is the function checkCapabilityAndAuthenticateUser of the file Core/Controller.php of the component Controller. Performing a manipulation results in improper authentication. The attack may be initiated remotely. Upgrading to version 1.10.0 is sufficient to resolve this issue. The patch is named 6fc91c49eebdb8bfdfeed71cb50a5d97eac70f24. It is advisable to upgrade the affected component.
{
"affected": [],
"aliases": [
"CVE-2026-86810"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-08T20:18:54Z",
"severity": "MODERATE"
},
"details": "A vulnerability was detected in Open-Web-Analytics up to 1.9.1. The impacted element is the function checkCapabilityAndAuthenticateUser of the file Core/Controller.php of the component Controller. Performing a manipulation results in improper authentication. The attack may be initiated remotely. Upgrading to version 1.10.0 is sufficient to resolve this issue. The patch is named 6fc91c49eebdb8bfdfeed71cb50a5d97eac70f24. It is advisable to upgrade the affected component.",
"id": "GHSA-vq6x-7g8m-7qhj",
"modified": "2026-09-08T21:34:30Z",
"published": "2026-09-08T21:34:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-86810"
},
{
"type": "WEB",
"url": "https://github.com/Open-Web-Analytics/Open-Web-Analytics/issues/959"
},
{
"type": "WEB",
"url": "https://github.com/Open-Web-Analytics/Open-Web-Analytics/pull/961"
},
{
"type": "WEB",
"url": "https://github.com/Open-Web-Analytics/Open-Web-Analytics/commit/6fc91c49eebdb8bfdfeed71cb50a5d97eac70f24"
},
{
"type": "WEB",
"url": "https://github.com/Open-Web-Analytics/Open-Web-Analytics"
},
{
"type": "WEB",
"url": "https://github.com/Open-Web-Analytics/Open-Web-Analytics/releases/tag/1.10.0"
},
{
"type": "WEB",
"url": "https://vuldb.com/cve/CVE-2026-86810"
},
{
"type": "WEB",
"url": "https://vuldb.com/submit/911107"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/399814"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/399814/cti"
}
],
"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"
}
]
}
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.