Shreemaan-Abhishek

Relative Path Traversal, with Unintended Proxy vulnerability in Apache APISIX. A caller of the MCP endpoint can invoke endpoints the OpenAPI document never declared, under the declared tool's HTTP method, using the credentials the Route adds. This issue affects Apache APISIX: from 3.19.0 before 3.20.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue.

توجد ثغرة لتجاوز المصادقة حيث يمكن لعميل غير مصرح له تزييف رأس الهوية. يحدث هذا في المسارات التي تستخدم `jwe-decrypt` عندما تكون قيمة `strict` مضبوطة على `false` ويكون `forward header` مختلفًا عن رأس الرمز (token header)، مما يسمح للعميل بتزويد قيمة يعاملها النظام الخلفي (upstream) كنص واضح تم فك تشفيره بواسطة البوابة. يمكن أن يحدث سيناريو مماثل عندما يتم تكوين `forward-auth` مع ضبط `allow degradation` على `true` وتكون خدمة المصادقة غير متاحة.

يوجد تعارض في التفسير ناتج عن عدم تطابق في تطبيع المسار (path normalization) بين التوجيه والتوجيه إلى الخادم الخلفي (upstream forwarding). يسمح هذا لعميل غير مصرح له بتجاوز إضافات المصادقة على مستوى المسار والوصول إلى مسارات الخادم الخلفي المحمية عندما يكون هناك مسار بدون مصادقة على نفس الخادم الخلفي، وبشرط ألا يقوم الخادم الخلفي بدمج مقاطع النقطة المشفرة.

Incorrect Authorization vulnerability in Apache APISIX. An authenticated user who holds any one of a route's required permissions or scopes can reach the protected upstream without the others, including HTTP methods the authorization server denied. This issue affects Apache APISIX: from 1.4.0 through 3.19.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue.

Authentication bypass by spoofing vulnerability in Apache APISIX. When a Route's configured headers carry a caller identity and the OpenAPI document declares the same header, a caller can act as another identity against the upstream API. This issue affects Apache APISIX: from 3.19.0 before 3.20.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue.

Interpretation Conflict, leading to Incorrect Authorization vulnerability in Apache APISIX. With match uri encoded slash enabled and skip mtls uri regex configured, a client without a certificate can reach an upstream behind a route that requires one, limited to request paths that decode to an exempted URI. This issue affects Apache APISIX: from 3.18.0 through 3.19.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue.

Authentication bypass by spoofing vulnerability in Apache APISIX. On a route where multi-auth falls back from wolf-rbac to another successful authenticator, client-supplied Wolf identity headers can remain in the request. A downstream service that relies on those documented headers may therefore receive an identity that was not established by the successful authenticator. This issue affects Apache APISIX: from 3.8.0 through 3.19.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue.

Cross-Site Request Forgery (CSRF) exists in the feishu-auth and dingtalk-auth plugins. An attacker can trick a user into clicking a crafted link, causing the user's browser session on a protected route to be established under the attacker's identity. Consequently, any actions performed by the user during that session, such as form submissions, uploads, or account bindings, will be associated with the attacker's account.

The `batch-requests` plugin contains a flaw where resources are allocated without limits or throttling. An unauthenticated caller can cause a gateway worker to experience Out of Memory (OOM)—a state where the system exhausts its available RAM—by targeting a route that utilizes the `batch-requests` plugin and has the `batch` endpoint publicly exposed.

An issue exists where the use of non-canonical URL paths for authorization decisions allows a crafted encoded path to reach an upstream endpoint. In configurations where a permissive route overlaps a protected one, requests that should be rejected are served instead, granting unauthenticated access to a protected upstream endpoint.

Improper Authentication occurs when using the openid-connect plugin with remote introspection against an authorization server that serves multiple issuers. In this scenario, a token that is active for one issuer may be incorrectly accepted on a route restricted to a different issuer.

An improper verification of cryptographic signatures occurs within the `saml-auth` plugin under default configuration. This allows an unauthenticated attacker to impersonate any user on every route protected by this plugin.