Edward Prior

اسم البرنامج المعرض للخطر والإصدارات المتأثرة: Octopus Deploy (الإصدارات المتأثرة غير محددة) الوصف: تسمح هذه الثغرة بتحميل الملفات إلى مواقع غير متوقعة على المضيف عبر نقطة نهاية واجهة برمجة التطبيقات (API). ويرجع ذلك إلى عدم وجود عملية التحقق من صحة البيانات في أحد الحقول، مما قد يؤدي إلى إيجاد طرق للتحايل على سير العمل المتوقع. التوصيات: في الوقت الحالي، لا توجد معلومات عن إصدار أحدث يحتوي على تصحيح لهذه الثغرة الأمنية.

اسم البرنامج المعرض للخطر والإصدارات المتأثرة: Octopus Server (الإصدارات المتأثرة غير محددة) الوصف: في الإصدارات المتأثرة من Octopus Server، يمكن للمستخدم الذي يتمتع بامتيازات وصول كافية تعيين رؤوس مخصصة في جميع استجابات الخادم. ومن خلال إرسال رأس ”referrer“ مصمم خصيصًا، يمكن للمستخدم ضمان أن جميع الاستجابات اللاحقة من الخادم ستُرجع أخطاء 500، مما يجعل الموقع غير قابل للاستخدام عمليًا. وبعد ذلك، يمكن للمستخدم تعيين رأس «referrer» وإزالته للتحكم في حالة رفض الخدمة باستخدام رمز CSRF صالح، في حين يتعذر إنشاء رموز CSRF جديدة. التوصيات: في الوقت الحالي، لا توجد معلومات عن إصدار أحدث يحتوي على تصحيح لهذه الثغرة الأمنية.

The issue is related to the absence of a warning when a user attempts to navigate to a new protocol handler under certain conditions. This could potentially allow a remote attacker to impact data integrity.

The issue is related to the disclosure of information through registration files, potentially exposing browsing habits of users running in a private tab. This could allow a remote attacker to reveal protected information. The estimated number of potentially affected devices worldwide is not specified.

The issue is related to the incorrect functioning of `ms-cxh` and `ms-cxh-full` protocol handlers, which could be leveraged to trigger a denial of service. This affects Windows operating systems. The exploitation of this issue may allow a remote attacker to cause the application to crash using a specially crafted website.

The issue allows for unauthenticated user enumeration by interacting with an unsecured endpoint to retrieve information on each account within the system.

The application was vulnerable to a session fixation that could be used to hijack accounts.

The application is vulnerable to an authenticated Stored Cross-Site Scripting (XSS) issue in its messaging functionality. This could lead to privilege escalation or the compromise of a targeted account.

The issue allows authenticated information disclosure, enabling administrators to view unsalted user passwords. This could lead to the compromise of plaintext passwords via offline attacks.

The application is susceptible to Server-Side Request Forgery attacks. This allows the backend server to interact with unexpected endpoints, which could include internal and local services. As a result, it may lead to attacks on other downstream systems.

The application has a CSV injection issue in its data export functionality. This allows malicious code to be embedded within the export data, which can then be triggered when the exported data is viewed.

The application is vulnerable to an authenticated Stored Cross-Site Scripting (XSS) issue in the user profile data fields. This could be used to escalate privileges within the application and compromise any account that views the affected user profile.

The application is affected by an authenticated Stored Cross-Site Scripting (XSS) issue in the upload and download functionality. This could allow attackers to escalate privileges or compromise accounts by coercing them into accessing targeted files.

The application is affected by an unauthenticated Reflected Cross-Site Scripting (XSS) vulnerability in the barcode generation functionality. This allows attackers to generate an unsafe link that could compromise users.

The application is vulnerable to Cross-Site Request Forgery (CSRF) attacks. This allows an attacker to coerce users into sending malicious requests to the site, potentially leading to account deletion or, in rare cases, account hijacking and the creation of additional admin accounts.