Nils Emmerich

تم اكتشاف ثغرة في ملحق Big Requests، حيث يتم ضرب طول الطلب في 4 قبل مقارنته بالحجم الأقصى المسموح به. وقد يؤدي ذلك إلى حدوث تجاوز سعة عدد صحيح، مما يسمح للمهاجم بالتحايل على فحص الحجم.

تم العثور على ثغرة في الملحق XFIXES. لا يقوم المعالج XFixesSetClientDisconnectMode بالتحقق من صحة حجم الطلب، مما يسمح للعميل بقراءة الذاكرة غير المخصصة من الطلبات السابقة.

تم اكتشاف ثغرة أمنية في معالجة المؤشرات المتحركة. إذا لم يقم العميل بتوفير أي مؤشر، يفترض الخادم وجود مؤشر واحد على الأقل، مما يؤدي إلى قراءة خارج النطاق واحتمال تعطل النظام.

تتعلق المشكلة بثغرة أمنية تتعلق بتسرب المعلومات، وهي نوع من المشكلات التي قد تؤدي إلى كشف معلومات حساسة بسبب ثغرة في البرنامج. قد تسمح هذه الثغرة بتسرب المعلومات الحساسة، مما قد يعرض أمن النظام للخطر.

تسمح هذه الثغرة للمهاجمين بتنفيذ تعليمات برمجية عشوائية عن طريق حقن حمولة مُعدَّلة في حقل `username` في رسالة بريد إلكتروني. هذه ثغرة تتعلق بحقن HTML.

تسمح ثغرة في المكون src/api/identity.rs في Vaultwarden للمهاجمين بانتحال هوية المستخدمين، بما في ذلك المسؤولين، عبر طلب تفويض مُعد خصيصًا. تتيح هذه الثغرة للمهاجمين التلاعب بطلبات التفويض للحصول على وصول غير مصرح به.

تتعلق المشكلة بثغرة أمنية من نوع «التنفيذ البرمجي عبر المواقع» (XSS) المنعكس والمصادق عليه. توجد هذه الثغرة في المكون /api/core/mod.rs.

The issue allows attackers to bypass all JWT-parsing signature checks by crafting a JWT with an `enc` header with the value `A256GCM`. This enables them to potentially access unauthorized resources or perform malicious actions.

A relative path traversal attack allows attackers with service user privileges to upload arbitrary files. By uploading a specially crafted tar file, an attacker can execute arbitrary commands.

The issue is related to improper access controls, allowing attackers to extract and tamper with the device's network configuration.

A vulnerability allows attackers to recover user credentials of the administrative interface.

A XPath injection issue allows unauthenticated remote attackers to access sensitive information and escalate privileges.

The issue allows user input to be validated on the client side without proper authentication by the server. This is problematic because the server should not rely solely on the correctness of the data sent by the client, as users may not support or block JavaScript, or could intentionally bypass the client-side checks. An attacker with knowledge of the service user could exploit this by circumventing the client-side control, potentially allowing them to login with service privileges.

An attacker with physical access to the host can extract secrets from the registry and create valid JWT tokens for the application, allowing them to impersonate arbitrary users. This could also enable the manipulation of RabbitMQ queues and messages by impersonating users.

The issue allows access to sensitive endpoints without requiring authentication information, such as a session cookie. This enables an attacker to send requests to these endpoints as an unauthenticated user, potentially performing critical actions or modifying critical configuration parameters.

The application layer encryption of the communication protocol between the Ypsomed mylife App and mylife Cloud uses non-random IVs, which allows man-in-the-middle attackers to tamper with messages.

The Ypsomed mylife Cloud discloses password hashes during the registration process.

The Ypsomed mylife Cloud reflects the user password during the login process after redirecting the user from a HTTPS endpoint to a HTTP endpoint.

Name of the Vulnerable Software and Affected Versions: Hamilton Medical AG T1-Ventillator versions 2.2.3 and prior Description: The issue is related to an XML validation vulnerability in the ventilator, allowing privileged attackers with physical access to render the device persistently unusable by uploading specially crafted configuration files. Recommendations: For Hamilton Medical AG T1-Ventillator versions 2.2.3 and prior, consider restricting physical access to the device to prevent exploitation of the XML validation vulnerability until a patch is available. As a temporary workaround, consider disabling the upload of configuration files to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: SOOIL Developments Co., Ltd Diabecare RS, AnyDana-i and AnyDana-A (affected versions not specified) Description: The communication protocol of the insulin pump and its AnyDana-i and AnyDana-A mobile applications lacks replay protection measures. This allows unauthenticated, physically proximate attackers to replay communication sequences via Bluetooth Low Energy. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.