Skip to content

Commit 4705069

Browse files
1 parent 8011175 commit 4705069

3 files changed

Lines changed: 200 additions & 4 deletions

File tree

advisories/unreviewed/2026/03/GHSA-fwj4-6wgp-mpxm/GHSA-fwj4-6wgp-mpxm.json renamed to advisories/github-reviewed/2026/03/GHSA-fwj4-6wgp-mpxm/GHSA-fwj4-6wgp-mpxm.json

Lines changed: 33 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,40 +1,69 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-fwj4-6wgp-mpxm",
4-
"modified": "2026-03-17T15:36:23Z",
4+
"modified": "2026-03-18T17:25:29Z",
55
"published": "2026-03-17T15:36:23Z",
66
"aliases": [
77
"CVE-2026-4324"
88
],
9+
"summary": "Katello: Denial of Service and potential information disclosure via SQL injection",
910
"details": "A flaw was found in the Katello plugin for Red Hat Satellite. This vulnerability, caused by improper sanitization of user-provided input, allows a remote attacker to inject arbitrary SQL commands into the sort_by parameter of the /api/hosts/bootc_images API endpoint. This can lead to a Denial of Service (DoS) by triggering database errors, and potentially enable Boolean-based Blind SQL injection, which could allow an attacker to extract sensitive information from the database.",
1011
"severity": [
1112
{
1213
"type": "CVSS_V3",
1314
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L"
1415
}
1516
],
16-
"affected": [],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "RubyGems",
21+
"name": "katello"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "0"
29+
},
30+
{
31+
"fixed": "4.19.1"
32+
}
33+
]
34+
}
35+
]
36+
}
37+
],
1738
"references": [
1839
{
1940
"type": "ADVISORY",
2041
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-4324"
2142
},
43+
{
44+
"type": "WEB",
45+
"url": "https://github.com/Katello/katello/commit/a0a793b08d4f0a897ee985d79a687ad043f99e57"
46+
},
2247
{
2348
"type": "WEB",
2449
"url": "https://access.redhat.com/security/cve/CVE-2026-4324"
2550
},
2651
{
2752
"type": "WEB",
2853
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2448349"
54+
},
55+
{
56+
"type": "PACKAGE",
57+
"url": "https://github.com/Katello/katello"
2958
}
3059
],
3160
"database_specific": {
3261
"cwe_ids": [
3362
"CWE-89"
3463
],
3564
"severity": "MODERATE",
36-
"github_reviewed": false,
37-
"github_reviewed_at": null,
65+
"github_reviewed": true,
66+
"github_reviewed_at": "2026-03-18T17:25:29Z",
3867
"nvd_published_at": "2026-03-17T14:16:19Z"
3968
}
4069
}
Lines changed: 110 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,110 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-g2pf-ww5m-2r9m",
4+
"modified": "2026-03-18T17:25:41Z",
5+
"published": "2026-03-18T17:25:41Z",
6+
"aliases": [
7+
"CVE-2026-33132"
8+
],
9+
"summary": "Zitadel is missing enforcement of organization scopes",
10+
"details": "### Summary\n\nA vulnerability in Zitadel's OAuth2/OIDC interface, which allowed users to bypass organization enforcement during authentication.\n\n### Impact\n\nZitadel allows applications to enforce an organzation context during authentication using [scopes](https://zitadel.com/docs/apis/openidoauth/scopes#reserved-scopes) (`urn:zitadel:iam:org:id:{id}` and `urn:zitadel:iam:org:domain:primary:{domainname}`). If enforced, a user needs to be part of the required organization to sign in.\n\nWhile this was properly enforced for OAuth2/OIDC authorization requests in login V1, corresponding controls were missing for device authorization requests and all login V2 and OIDC API V2 endpoints.\nThis allowed users to bypass the restriction and sign in with users from other organizations.\n\nNote that this enforcement allows for an additional check during authentication and applications relying on authorizations / roles assignments are not affected by this bypass.\n\n### Affected Versions\n\nSystems running one of the following versions are affected:\n- **4.x**: `4.0.0` through `4.12.2` (including RC versions)\n- **3.x**: `3.0.0` through `3.4.8` (including RC versions)\n\n### Patches\n\nThe vulnerability has been addressed in the latest releases. The patch resolves the issue by validating the provided scopes and enforcing the organization existence when processing the authorization request. Additionally it will prevent the use of a session of a user which does not belong to the required organization on the OIDC service endpoints ([CreateCallback](https://zitadel.com/docs/reference/api/oidc/zitadel.oidc.v2.OIDCService.CreateCallback) and [Authorize or Deny Device Authorization](https://zitadel.com/docs/reference/api/oidc/zitadel.oidc.v2.OIDCService.AuthorizeOrDenyDeviceAuthorization) endpoints).\n\n4.x: Upgrade to >=[4.12.3](https://github.com/zitadel/zitadel/releases/tag/v4.12.3)\n3.x: Update to >=[3.4.9](https://github.com/zitadel/zitadel/releases/tag/v3.4.9)\n\n### Workarounds\n\nThe recommended solution is to upgrade to a patched version. \n\n### Questions\n\nIf you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)\n\n### Credits\n\nThanks to @motoki317 for reporting this vulnerability.",
11+
"severity": [
12+
{
13+
"type": "CVSS_V3",
14+
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "Go",
21+
"name": "github.com/zitadel/zitadel"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "4.0.0-rc.1"
29+
},
30+
{
31+
"fixed": "4.12.3"
32+
}
33+
]
34+
}
35+
],
36+
"database_specific": {
37+
"last_known_affected_version_range": "<= 4.12.2"
38+
}
39+
},
40+
{
41+
"package": {
42+
"ecosystem": "Go",
43+
"name": "github.com/zitadel/zitadel"
44+
},
45+
"ranges": [
46+
{
47+
"type": "ECOSYSTEM",
48+
"events": [
49+
{
50+
"introduced": "3.0.0-rc.1"
51+
},
52+
{
53+
"fixed": "3.4.9"
54+
}
55+
]
56+
}
57+
]
58+
},
59+
{
60+
"package": {
61+
"ecosystem": "Go",
62+
"name": "github.com/zitadel/zitadel"
63+
},
64+
"ranges": [
65+
{
66+
"type": "ECOSYSTEM",
67+
"events": [
68+
{
69+
"introduced": "0"
70+
},
71+
{
72+
"fixed": "1.80.0-v2.20.0.20260317120401-d90285929ca0"
73+
}
74+
]
75+
}
76+
]
77+
}
78+
],
79+
"references": [
80+
{
81+
"type": "WEB",
82+
"url": "https://github.com/zitadel/zitadel/security/advisories/GHSA-g2pf-ww5m-2r9m"
83+
},
84+
{
85+
"type": "WEB",
86+
"url": "https://github.com/zitadel/zitadel/commit/d90285929ca019fa817f31551fd0883429dda2a8"
87+
},
88+
{
89+
"type": "PACKAGE",
90+
"url": "https://github.com/zitadel/zitadel"
91+
},
92+
{
93+
"type": "WEB",
94+
"url": "https://github.com/zitadel/zitadel/releases/tag/v3.4.9"
95+
},
96+
{
97+
"type": "WEB",
98+
"url": "https://github.com/zitadel/zitadel/releases/tag/v4.12.3"
99+
}
100+
],
101+
"database_specific": {
102+
"cwe_ids": [
103+
"CWE-863"
104+
],
105+
"severity": "MODERATE",
106+
"github_reviewed": true,
107+
"github_reviewed_at": "2026-03-18T17:25:41Z",
108+
"nvd_published_at": null
109+
}
110+
}
Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-g5ph-f57v-mwjc",
4+
"modified": "2026-03-18T17:25:02Z",
5+
"published": "2026-03-18T17:25:02Z",
6+
"aliases": [
7+
"CVE-2026-33143"
8+
],
9+
"summary": "OneUptime WhatsApp Webhook Missing Signature Verification",
10+
"details": "### Summary\n\nThe WhatsApp POST webhook handler (`/notification/whatsapp/webhook`) processes incoming status update events without verifying the Meta/WhatsApp `X-Hub-Signature-256` HMAC signature, allowing any unauthenticated attacker to send forged webhook payloads that manipulate notification delivery status records, suppress alerts, and corrupt audit trails. The codebase already implements proper signature verification for Slack webhooks.\n\n### Details\n\n**Vulnerable code — `App/FeatureSet/Notification/API/WhatsApp.ts` lines 372-430:**\n```typescript\nrouter.post(\n \"/webhook\",\n async (req: ExpressRequest, res: ExpressResponse, next: NextFunction) => {\n try {\n const body: JSONObject = req.body as JSONObject;\n // NO signature verification! No X-Hub-Signature-256 check!\n\n if (\n (body[\"object\"] as string | undefined) !== \"whatsapp_business_account\"\n ) {\n return Response.sendEmptySuccessResponse(req, res);\n }\n\n const entries: JSONArray | undefined = body[\"entry\"] as JSONArray | undefined;\n // ... processes entries and updates WhatsApp log status records\n```\n\nCompare with the Slack webhook which correctly validates signatures:\n\n**`Common/Server/Middleware/SlackAuthorization.ts` line 58:**\n```typescript\nconst isValid = crypto.timingSafeEqual(\n Buffer.from(computedSignature),\n Buffer.from(slackSignature)\n);\n```\n\nThe WhatsApp GET webhook correctly validates the verify token — only the POST handler (which processes actual events) is missing signature verification.\n\nNo existing CVEs cover webhook signature verification issues in OneUptime. The closest is GHSA-cw6x-mw64-q6pv (WhatsApp Resend Verification Auth Bypass), which is about a different WhatsApp-related authorization issue.\n\n### PoC\n\n**Environment:** OneUptime v10.0.23 via `docker compose up` (default configuration)\n\n```bash\n# Forge a delivery status update for any WhatsApp notification — no auth, no signature\ncurl -sv -X POST http://TARGET:8080/api/notification/whatsapp/webhook \\\n -H \"Content-Type: application/json\" \\\n -d '{\n \"object\": \"whatsapp_business_account\",\n \"entry\": [{\n \"id\": \"FAKE_WABA_ID\",\n \"changes\": [{\n \"value\": {\n \"messaging_product\": \"whatsapp\",\n \"metadata\": {\n \"display_phone_number\": \"+15550000000\",\n \"phone_number_id\": \"FAKE_PHONE_ID\"\n },\n \"messages\": [{\n \"from\": \"15551234567\",\n \"id\": \"wamid.FAKE\",\n \"timestamp\": \"1234567890\",\n \"text\": {\"body\": \"INJECTED_MESSAGE\"},\n \"type\": \"text\"\n }]\n },\n \"field\": \"messages\"\n }]\n }]\n }'\n```\n\n**Docker validation (oneuptime/app:release, APP_VERSION=10.0.23):**\n```\n< HTTP/1.1 200 OK\n{}\n```\n\n- Fake WhatsApp webhook payload accepted with HTTP 200\n- No `X-Hub-Signature-256` header provided — no signature verification at all\n- Attacker can inject arbitrary inbound WhatsApp messages and forge delivery status updates\n\n### Impact\n\nAny unauthenticated remote attacker can forge WhatsApp webhook events:\n\n- **False delivery status:** Mark undelivered WhatsApp notifications as \"delivered\", hiding delivery failures from administrators\n- **Alert suppression:** Critical on-call notifications that failed to deliver appear successful, preventing escalation\n- **Log manipulation:** WhatsApp notification logs updated with forged status data, corrupting audit trails\n- **Incident response disruption:** During active incidents, forging \"delivered\" statuses prevents the system from retrying failed notification deliveries",
11+
"severity": [
12+
{
13+
"type": "CVSS_V4",
14+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "npm",
21+
"name": "oneuptime"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "0"
29+
},
30+
{
31+
"fixed": "10.0.34"
32+
}
33+
]
34+
}
35+
]
36+
}
37+
],
38+
"references": [
39+
{
40+
"type": "WEB",
41+
"url": "https://github.com/OneUptime/oneuptime/security/advisories/GHSA-g5ph-f57v-mwjc"
42+
},
43+
{
44+
"type": "PACKAGE",
45+
"url": "https://github.com/OneUptime/oneuptime"
46+
}
47+
],
48+
"database_specific": {
49+
"cwe_ids": [
50+
"CWE-345"
51+
],
52+
"severity": "HIGH",
53+
"github_reviewed": true,
54+
"github_reviewed_at": "2026-03-18T17:25:02Z",
55+
"nvd_published_at": null
56+
}
57+
}

0 commit comments

Comments
 (0)