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.
6040 vulnerabilities reference this CWE, most recent first.
GHSA-5F5V-X476-84XC
Vulnerability from github – Published: 2022-05-17 04:04 – Updated: 2022-05-17 04:04The default configuration of Cisco Small Business IP phones SPA 300 7.5.5 and SPA 500 7.5.5 does not properly support authentication, which allows remote attackers to read audio-stream data or originate telephone calls via a crafted XML request, aka Bug ID CSCuo52482.
{
"affected": [],
"aliases": [
"CVE-2015-0670"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2015-03-21T01:59:00Z",
"severity": "MODERATE"
},
"details": "The default configuration of Cisco Small Business IP phones SPA 300 7.5.5 and SPA 500 7.5.5 does not properly support authentication, which allows remote attackers to read audio-stream data or originate telephone calls via a crafted XML request, aka Bug ID CSCuo52482.",
"id": "GHSA-5f5v-x476-84xc",
"modified": "2022-05-17T04:04:30Z",
"published": "2022-05-17T04:04:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2015-0670"
},
{
"type": "WEB",
"url": "http://tools.cisco.com/security/center/viewAlert.x?alertId=37946"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id/1031969"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-5F64-WWGV-QHFQ
Vulnerability from github – Published: 2022-05-02 00:00 – Updated: 2022-05-02 00:00Session fixation vulnerability in phpFreeChat 1.1 allows remote authenticated users to hijack web sessions by setting the session_id parameter to match the victim's nickid parameter.
{
"affected": [],
"aliases": [
"CVE-2008-3428"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2008-07-31T22:41:00Z",
"severity": "MODERATE"
},
"details": "Session fixation vulnerability in phpFreeChat 1.1 allows remote authenticated users to hijack web sessions by setting the session_id parameter to match the victim\u0027s nickid parameter.",
"id": "GHSA-5f64-wwgv-qhfq",
"modified": "2022-05-02T00:00:06Z",
"published": "2022-05-02T00:00:06Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-3428"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/44116"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/31283"
},
{
"type": "WEB",
"url": "http://www.phpfreechat.net/changelog/1.2"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/30462"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-5FCQ-R7M3-PXF5
Vulnerability from github – Published: 2022-04-30 18:10 – Updated: 2025-04-03 03:33In some cases, Service Pack 4 for Windows NT 4.0 can allow access to network shares using a blank password, through a problem with a null NT hash value.
{
"affected": [],
"aliases": [
"CVE-1999-0366"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "1999-02-08T05:00:00Z",
"severity": "HIGH"
},
"details": "In some cases, Service Pack 4 for Windows NT 4.0 can allow access to network shares using a blank password, through a problem with a null NT hash value.",
"id": "GHSA-5fcq-r7m3-pxf5",
"modified": "2025-04-03T03:33:34Z",
"published": "2022-04-30T18:10:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-1999-0366"
},
{
"type": "WEB",
"url": "https://docs.microsoft.com/en-us/security-updates/securitybulletins/1999/ms99-004"
},
{
"type": "WEB",
"url": "http://support.microsoft.com/default.aspx?scid=kb%3B%5BLN%5D%3BQ214840"
},
{
"type": "WEB",
"url": "http://support.microsoft.com/default.aspx?scid=kb;[LN];Q214840"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-5FFH-V4JR-F65H
Vulnerability from github – Published: 2026-05-18 18:31 – Updated: 2026-05-18 18:31Improper authentication in Azure Local Disconnected Operations allows an unauthorized attacker to elevate privileges over a network.
{
"affected": [],
"aliases": [
"CVE-2026-42822"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-18T18:17:34Z",
"severity": "CRITICAL"
},
"details": "Improper authentication in Azure Local Disconnected Operations allows an unauthorized attacker to elevate privileges over a network.",
"id": "GHSA-5ffh-v4jr-f65h",
"modified": "2026-05-18T18:31:30Z",
"published": "2026-05-18T18:31:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42822"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-42822"
}
],
"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-5FFJ-X2FF-2JP7
Vulnerability from github – Published: 2022-05-17 04:16 – Updated: 2022-05-17 04:16The rsync daemon in F5 BIG-IP 11.6 before 11.6.0, 11.5.1 before HF3, 11.5.0 before HF4, 11.4.1 before HF4, 11.4.0 before HF7, 11.3.0 before HF9, and 11.2.1 before HF11 and Enterprise Manager 3.x before 3.1.1 HF2, when configured in failover mode, does not require authentication, which allows remote attackers to read or write to arbitrary files via a cmi request to the ConfigSync IP address.
{
"affected": [],
"aliases": [
"CVE-2014-2927"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2014-10-15T14:55:00Z",
"severity": "HIGH"
},
"details": "The rsync daemon in F5 BIG-IP 11.6 before 11.6.0, 11.5.1 before HF3, 11.5.0 before HF4, 11.4.1 before HF4, 11.4.0 before HF7, 11.3.0 before HF9, and 11.2.1 before HF11 and Enterprise Manager 3.x before 3.1.1 HF2, when configured in failover mode, does not require authentication, which allows remote attackers to read or write to arbitrary files via a cmi request to the ConfigSync IP address.",
"id": "GHSA-5ffj-x2ff-2jp7",
"modified": "2022-05-17T04:16:58Z",
"published": "2022-05-17T04:16:58Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2014-2927"
},
{
"type": "WEB",
"url": "https://support.f5.com/kb/en-us/solutions/public/15000/200/sol15236.html"
},
{
"type": "WEB",
"url": "http://www.exploit-db.com/exploits/34465"
},
{
"type": "WEB",
"url": "http://www.security-assessment.com/files/documents/advisory/F5_Unauthenticated_rsync_access_to_Remote_Root_Code_Execution.pdf"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-5FG6-WRQ4-W5GH
Vulnerability from github – Published: 2026-03-12 14:47 – Updated: 2026-03-12 14:47VULNERABILITY: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass
Severity: CRITICAL CVSS 3.1: 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) CWE: CWE-287 (Improper Authentication) Component: internal/home/web.go Affected: AdGuardHome (tested on v0.107.72)
Summary
An unauthenticated remote attacker can bypass all authentication in AdGuardHome by sending an HTTP/1.1 request that requests an upgrade to HTTP/2 cleartext (h2c). Once the upgrade is accepted, the resulting HTTP/2 connection is handled by the inner mux, which has no authentication middleware attached. All subsequent HTTP/2 requests on that connection are processed as fully authenticated, regardless of whether any credentials were provided.
Root Cause
In internal/home/web.go (approximately lines 268-283), the HTTP server is constructed as follows: hdlr := h2c.NewHandler( withMiddlewares(web.conf.mux, limitRequestBody), // no auth &http2.Server{}, ) web.httpServer = &http.Server{ Handler: web.auth.middleware().Wrap(hdlr), // auth here }
The authentication middleware wraps the h2c handler at the outer layer. When an h2c upgrade request arrives, the h2c library hijacks the TCP connection and calls http2.ServeConn with Handler set to the inner mux, which was stored at h2c.NewHandler creation time. The authentication middleware is never consulted for any request sent over the resulting HTTP/2 connection. The upgrade request itself passes through because it targets a public path (such as /control/login), which is whitelisted by isPublicResource() in internal/home/authhttp.go. After the upgrade, the attacker can reach any administrative endpoint.
Proof of Concept
The PoC script (https://gist.github.com/mandreko/f742d244dfa452e8d00cc5736cf8d629) demonstrates the bypass using a raw TCP connection with HTTP/2 framing. No credentials are provided at any point.
Steps: 1. Open TCP connection to AdGuardHome (default port 3000). 2. Send HTTP/1.1 GET /control/login with headers: Upgrade: h2c Connection: Upgrade, HTTP2-Settings HTTP2-Settings: AAMAAABkAAQAAP__ 3. Server responds: 101 Switching Protocols. 4. Complete HTTP/2 handshake (client preface + SETTINGS exchange). 5. Send HTTP/2 HEADERS frame requesting GET /control/status on stream 3. 6. Server responds: HTTP 200 with full JSON status payload.
Sample output (no username or password supplied): python3 poc_h2c_auth_bypass.py 192.168.1.15 80 --hijack-dns 8.8.8.8 ==================================================================== AdGuardHome -- h2c Authentication Bypass PoC CWE-287: Full API access without credentials ==================================================================== Target : http://192.168.1.15:80 Upgrade : /control/login (whitelisted public path)
[*] Connecting and performing h2c upgrade ... [+] Bypass established -- authentication is not enforced
[*] GET /control/status [+] Version : v0.107.72 [+] DNS addresses: ['127.0.0.1', '::1', '192.168.1.15', 'fd64:b28c:45d2:4b5e:d35c:7660:e1b:92', 'fe80::ba65:3afa:617f:f077%eth0'] [+] HTTP port : 80 [+] Protection : ON
[*] GET /control/querylog (DNS query history) [+] 10 recent entries: 2026-03-09T20:42:15 docker.home.andreko.net 192.168.1.232 2026-03-09T20:42:00 docker.home.andreko.net 192.168.1.232 2026-03-09T20:41:45 docker.home.andreko.net 192.168.1.232 2026-03-09T20:41:30 docker.home.andreko.net 192.168.1.232 2026-03-09T20:41:12 docker.home.andreko.net 192.168.1.232
[*] GET /control/dhcp/status (network device inventory) [+] Dynamic leases : 0 [+] Static leases : 0
[*] POST /control/dns_config (DNS -> 8.8.8.8) [+] Upstream DNS changed to 8.8.8.8 [+] All DNS queries now route through attacker-controlled server
The bypass gives full administrative API access, including: - Reading and modifying DNS configuration - Adding malicious filter lists - Disabling protection - Changing the admin password - Hijacking DNS resolution for all clients on the network
Remediation
Move the authentication middleware inside the h2c handler so it applies to all connections regardless of protocol: authedMux := web.auth.middleware().Wrap( withMiddlewares(web.conf.mux, limitRequestBody), ) hdlr := h2c.NewHandler(authedMux, &http2.Server{}) web.httpServer = &http.Server{ Handler: hdlr, }
Alternatively, if h2c support is not required, removing h2c.NewHandler entirely would eliminate the attack surface. HTTP/2 over TLS (h2) is not affected by this vulnerability.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/AdguardTeam/AdGuardHome"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.107.73"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-32136"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-12T14:47:48Z",
"nvd_published_at": "2026-03-11T22:16:33Z",
"severity": "CRITICAL"
},
"details": "VULNERABILITY: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass\n========================================================================\nSeverity: \u00a0CRITICAL\nCVSS 3.1: \u00a09.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)\nCWE: \u00a0 \u00a0 \u00a0 CWE-287 (Improper Authentication)\nComponent: internal/home/web.go\nAffected: \u00a0AdGuardHome (tested on v0.107.72)\n\n------------------------------------------------------------------------\nSummary\n------------------------------------------------------------------------\n\nAn unauthenticated remote attacker can bypass all authentication in AdGuardHome by sending an HTTP/1.1 request that requests an upgrade to HTTP/2 cleartext (h2c). Once the upgrade is accepted, the resulting HTTP/2 connection is handled by the inner mux, which has no authentication middleware attached. All subsequent HTTP/2 requests on that connection are processed as fully authenticated, regardless of whether any credentials were provided.\n\n------------------------------------------------------------------------\nRoot Cause\n------------------------------------------------------------------------\n\nIn internal/home/web.go (approximately lines 268-283), the HTTP server is constructed as follows:\n\u00a0 \u00a0 hdlr := h2c.NewHandler(\n\u00a0 \u00a0 \u00a0 \u00a0 withMiddlewares(web.conf.mux, limitRequestBody), \u00a0// no auth\n\u00a0 \u00a0 \u00a0 \u00a0 \u0026http2.Server{},\n\u00a0 \u00a0 )\n\u00a0 \u00a0 web.httpServer = \u0026http.Server{\n\u00a0 \u00a0 \u00a0 \u00a0 Handler: web.auth.middleware().Wrap(hdlr), \u00a0 \u00a0 \u00a0 \u00a0// auth here\n\u00a0 \u00a0 }\n\nThe authentication middleware wraps the h2c handler at the outer layer. When an h2c upgrade request arrives, the h2c library hijacks the TCP connection and calls http2.ServeConn with Handler set to the inner mux, which was stored at h2c.NewHandler creation time. The authentication middleware is never consulted for any request sent over the resulting HTTP/2 connection. The upgrade request itself passes through because it targets a public path (such as /control/login), which is whitelisted by isPublicResource() in internal/home/authhttp.go. After the upgrade, the attacker can reach any administrative endpoint.\n\n------------------------------------------------------------------------\nProof of Concept\n------------------------------------------------------------------------\n\nThe PoC script (https://gist.github.com/mandreko/f742d244dfa452e8d00cc5736cf8d629) demonstrates the bypass using a raw TCP connection with HTTP/2 framing. No credentials are provided at any point.\n\nSteps:\n\u00a0 1. Open TCP connection to AdGuardHome (default port 3000).\n\u00a0 2. Send HTTP/1.1 GET /control/login with headers:\n\u00a0 \u00a0 \u00a0 \u00a0Upgrade: h2c\n\u00a0 \u00a0 \u00a0 \u00a0Connection: Upgrade, HTTP2-Settings\n\u00a0 \u00a0 \u00a0 \u00a0HTTP2-Settings: AAMAAABkAAQAAP__\n\u00a0 3. Server responds: 101 Switching Protocols.\n\u00a0 4. Complete HTTP/2 handshake (client preface + SETTINGS exchange).\n\u00a0 5. Send HTTP/2 HEADERS frame requesting GET /control/status on stream 3.\n\u00a0 6. Server responds: HTTP 200 with full JSON status payload.\n\nSample output (no username or password supplied):\n\u00a0 \u00a0 python3 poc_h2c_auth_bypass.py 192.168.1.15 80 --hijack-dns 8.8.8.8\n\u00a0 \u00a0 ====================================================================\n\u00a0 \u00a0 AdGuardHome -- h2c Authentication Bypass PoC\n\u00a0 \u00a0 CWE-287: Full API access without credentials\n\u00a0 \u00a0 ====================================================================\n\u00a0 \u00a0 Target \u00a0: [http://192.168.1.15:80](http://192.168.1.15/)\n\u00a0 \u00a0 Upgrade : /control/login \u00a0(whitelisted public path)\n\n\u00a0 \u00a0 [*] Connecting and performing h2c upgrade ...\n\u00a0 \u00a0 [+] Bypass established -- authentication is not enforced\n\n\u00a0 \u00a0 [*] GET /control/status\n\u00a0 \u00a0 [+] Version \u00a0 \u00a0 \u00a0: v0.107.72\n\u00a0 \u00a0 [+] DNS addresses: [\u0027127.0.0.1\u0027, \u0027::1\u0027, \u0027192.168.1.15\u0027, \u0027fd64:b28c:45d2:4b5e:d35c:7660:e1b:92\u0027, \u0027fe80::ba65:3afa:617f:f077%eth0\u0027]\n\u00a0 \u00a0 [+] HTTP port \u00a0 \u00a0: 80\n\u00a0 \u00a0 [+] Protection \u00a0 : ON\n\n\u00a0 \u00a0 [*] GET /control/querylog \u00a0(DNS query history)\n\u00a0 \u00a0 [+] 10 recent entries:\n\u00a0 \u00a0 \u00a0 \u00a0 2026-03-09T20:42:15 \u00a0[docker.home.andreko.net](http://docker.home.andreko.net/) \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 192.168.1.232\n\u00a0 \u00a0 \u00a0 \u00a0 2026-03-09T20:42:00 \u00a0[docker.home.andreko.net](http://docker.home.andreko.net/) \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 192.168.1.232\n\u00a0 \u00a0 \u00a0 \u00a0 2026-03-09T20:41:45 \u00a0[docker.home.andreko.net](http://docker.home.andreko.net/) \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 192.168.1.232\n\u00a0 \u00a0 \u00a0 \u00a0 2026-03-09T20:41:30 \u00a0[docker.home.andreko.net](http://docker.home.andreko.net/) \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 192.168.1.232\n\u00a0 \u00a0 \u00a0 \u00a0 2026-03-09T20:41:12 \u00a0[docker.home.andreko.net](http://docker.home.andreko.net/) \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 192.168.1.232\n\n\u00a0 \u00a0 [*] GET /control/dhcp/status \u00a0(network device inventory)\n\u00a0 \u00a0 [+] Dynamic leases : 0\n\u00a0 \u00a0 [+] Static leases \u00a0: 0\n\n\u00a0 \u00a0 [*] POST /control/dns_config \u00a0(DNS -\u003e 8.8.8.8)\n\u00a0 \u00a0 [+] Upstream DNS changed to 8.8.8.8\n\u00a0 \u00a0 [+] All DNS queries now route through attacker-controlled server\n\nThe bypass gives full administrative API access, including:\n\u00a0 - Reading and modifying DNS configuration\n\u00a0 - Adding malicious filter lists\n\u00a0 - Disabling protection\n\u00a0 - Changing the admin password\n\u00a0 - Hijacking DNS resolution for all clients on the network\n\n------------------------------------------------------------------------\nRemediation\n------------------------------------------------------------------------\n\nMove the authentication middleware inside the h2c handler so it applies to all connections regardless of protocol:\n\u00a0 \u00a0 authedMux := web.auth.middleware().Wrap(\n\u00a0 \u00a0 \u00a0 \u00a0 withMiddlewares(web.conf.mux, limitRequestBody),\n\u00a0 \u00a0 )\n\u00a0 \u00a0 hdlr := h2c.NewHandler(authedMux, \u0026http2.Server{})\n\u00a0 \u00a0 web.httpServer = \u0026http.Server{\n\u00a0 \u00a0 \u00a0 \u00a0 Handler: hdlr,\n\u00a0 \u00a0 }\n\nAlternatively, if h2c support is not required, removing h2c.NewHandler entirely would eliminate the attack surface. HTTP/2 over TLS (h2) is not affected by this vulnerability.",
"id": "GHSA-5fg6-wrq4-w5gh",
"modified": "2026-03-12T14:47:48Z",
"published": "2026-03-12T14:47:48Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/AdguardTeam/AdGuardHome/security/advisories/GHSA-5fg6-wrq4-w5gh"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32136"
},
{
"type": "PACKAGE",
"url": "https://github.com/AdguardTeam/AdGuardHome"
}
],
"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"
}
],
"summary": "AdGuard Home: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass"
}
GHSA-5FH3-4CPH-HP6V
Vulnerability from github – Published: 2022-05-13 01:46 – Updated: 2022-05-13 01:46AIRTAME HDMI dongle with firmware before 2.2.0 allows unauthenticated access to a big part of the management interface. It is possible to extract all information including the Wi-Fi password, reboot, or force a software update at an arbitrary time.
{
"affected": [],
"aliases": [
"CVE-2017-7450"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-04-05T23:59:00Z",
"severity": "CRITICAL"
},
"details": "AIRTAME HDMI dongle with firmware before 2.2.0 allows unauthenticated access to a big part of the management interface. It is possible to extract all information including the Wi-Fi password, reboot, or force a software update at an arbitrary time.",
"id": "GHSA-5fh3-4cph-hp6v",
"modified": "2022-05-13T01:46:58Z",
"published": "2022-05-13T01:46:58Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-7450"
},
{
"type": "WEB",
"url": "http://cweiske.de/tagebuch/airtame-security.htm"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-5FHC-R7RJ-6CHF
Vulnerability from github – Published: 2022-05-24 19:08 – Updated: 2022-05-24 19:08iDrive RemotePC before 7.6.48 on Windows allows authentication bypass. A remote and unauthenticated attacker can bypass cloud authentication to connect and control a system via TCP port 5970 and 5980.
{
"affected": [],
"aliases": [
"CVE-2021-34690"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-07-15T14:15:00Z",
"severity": "CRITICAL"
},
"details": "iDrive RemotePC before 7.6.48 on Windows allows authentication bypass. A remote and unauthenticated attacker can bypass cloud authentication to connect and control a system via TCP port 5970 and 5980.",
"id": "GHSA-5fhc-r7rj-6chf",
"modified": "2022-05-24T19:08:12Z",
"published": "2022-05-24T19:08:12Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-34690"
},
{
"type": "WEB",
"url": "https://raw.githubusercontent.com/jacob-baines/vuln_disclosure/main/vuln_2021_01.txt"
},
{
"type": "WEB",
"url": "https://www.remotepc.com/release-info"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-5FHW-RC3X-VMXM
Vulnerability from github – Published: 2022-05-13 01:30 – Updated: 2025-04-20 03:33The "OpenID Connect Relying Party and OAuth 2.0 Resource Server" (aka mod_auth_openidc) module before 2.1.5 for the Apache HTTP Server does not skip OIDC_CLAIM_ and OIDCAuthNHeader headers in an "OIDCUnAuthAction pass" configuration, which allows remote attackers to bypass authentication via crafted HTTP traffic.
{
"affected": [],
"aliases": [
"CVE-2017-6062"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-03-02T06:59:00Z",
"severity": "HIGH"
},
"details": "The \"OpenID Connect Relying Party and OAuth 2.0 Resource Server\" (aka mod_auth_openidc) module before 2.1.5 for the Apache HTTP Server does not skip OIDC_CLAIM_ and OIDCAuthNHeader headers in an \"OIDCUnAuthAction pass\" configuration, which allows remote attackers to bypass authentication via crafted HTTP traffic.",
"id": "GHSA-5fhw-rc3x-vmxm",
"modified": "2025-04-20T03:33:32Z",
"published": "2022-05-13T01:30:59Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-6062"
},
{
"type": "WEB",
"url": "https://github.com/pingidentity/mod_auth_openidc/issues/222"
},
{
"type": "WEB",
"url": "https://github.com/pingidentity/mod_auth_openidc/blob/master/ChangeLog"
},
{
"type": "WEB",
"url": "https://github.com/pingidentity/mod_auth_openidc/releases/tag/v2.1.5"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/2V3HIGXMUKJGOBMAQAQPGC7G5YYWSUVA"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EJXBG3DG2FUYFGTUTSJFMPIINVFKKB4Z"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WTWUMQ46GZY3O4WU4JCF333LN53R2XQH"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2V3HIGXMUKJGOBMAQAQPGC7G5YYWSUVA"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EJXBG3DG2FUYFGTUTSJFMPIINVFKKB4Z"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WTWUMQ46GZY3O4WU4JCF333LN53R2XQH"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-5FMM-QCG5-XXR7
Vulnerability from github – Published: 2022-04-05 00:00 – Updated: 2022-04-12 00:00Improper authorization in GitLab Pages included with GitLab CE/EE affecting all versions from 11.5 prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2 allowed an attacker to steal a user's access token on an attacker-controlled private GitLab Pages website and reuse that token on the victim's other private websites
{
"affected": [],
"aliases": [
"CVE-2022-1148"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-04-04T20:15:00Z",
"severity": "MODERATE"
},
"details": "Improper authorization in GitLab Pages included with GitLab CE/EE affecting all versions from 11.5 prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2 allowed an attacker to steal a user\u0027s access token on an attacker-controlled private GitLab Pages website and reuse that token on the victim\u0027s other private websites",
"id": "GHSA-5fmm-qcg5-xxr7",
"modified": "2022-04-12T00:00:52Z",
"published": "2022-04-05T00:00:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-1148"
},
{
"type": "WEB",
"url": "https://hackerone.com/reports/1439552"
},
{
"type": "WEB",
"url": "https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-1148.json"
},
{
"type": "WEB",
"url": "https://gitlab.com/gitlab-org/gitlab/-/issues/350687"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
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.