Mal

اسم البرنامج المعرض للخطر والإصدارات المتأثرة: PAN-OS (الإصدارات المتأثرة غير محددة) الوصف: تسمح مشكلة تتعلق بعدم معالجة المدخلات بشكل سليم في واجهة الويب الخاصة بإدارة برنامج Palo Alto Networks PAN-OS لمسؤول خبيث، تم توثيقه بامتيازات القراءة والكتابة، بانتحال صفة مسؤول آخر شرعي تم توثيقه في PAN-OS. يجب أن يتمتع المهاجم بإمكانية الوصول عبر الشبكة إلى واجهة الويب الخاصة بالإدارة لاستغلال هذه المشكلة. يمكن تقليل مخاطر هذه المشكلة عن طريق تقييد الوصول إلى واجهة الويب الخاصة بالإدارة على عناوين IP الداخلية الموثوقة فقط. لا تؤثر هذه المشكلة على Cloud NGFW وجميع مثيلات Prisma Access. التوصيات: في الوقت الحالي، لا توجد معلومات عن إصدار أحدث يحتوي على تصحيح لهذه الثغرة الأمنية. كحل بديل مؤقت، يُنصح بتقييد الوصول إلى واجهة الويب الإدارية على عناوين IP الداخلية الموثوقة فقط، وفقًا لإرشادات النشر الحرجة الموصى بها.

تتعلق المشكلة بحقن القوالب من جانب الخادم (TSI) الذي يؤثر على المكون الإضافي للتجارة الإلكترونية، مما قد يؤدي إلى إمكانية تنفيذ التعليمات البرمجية عن بُعد (RCE).

Name of the Vulnerable Software and Affected Versions: PAN-OS (affected versions not specified) Description: The issue is related to an improper neutralization of matching symbols in the command line interface (CLI) of PAN-OS, which allows authenticated administrators, including those with read-only access, to read arbitrary files on the firewall. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

The issue is related to improper input validation in Apache Superset, allowing an authenticated attacker to create a MariaDB connection with local infile enabled. If both the MariaDB server and the local mysql client on the web server are set to allow for local infile, it's possible for the attacker to execute a specific MySQL/MariaDB SQL command that can read files from the server and insert their content into a MariaDB database table.

The vCenter Server contains multiple local privilege escalation issues due to a misconfiguration of `sudo`. An authenticated local user with non-administrative privileges may be able to exploit these issues to elevate privileges to root on the vCenter Server Appliance. A proof-of-concept exploit has been published and is available online. Approximately 40,000 systems are potentially affected. The root cause of the issue is a misconfiguration in the `/etc/sudoers` file, which allows for the preservation of dangerous environment variables during `sudo` command execution.

Name of the Vulnerable Software and Affected Versions: VMware vCenter Server (affected versions not specified) Description: The vCenter Server contains an authenticated remote code execution vulnerability. A malicious actor with administrative privileges on the vCenter appliance shell may exploit this issue to run arbitrary commands on the underlying operating system. A proof-of-concept (PoC) exploit has been released for this vulnerability, potentially allowing authenticated remote code execution. Recommendations: 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: vCenter Server (affected versions not specified) Description: The issue is related to insufficient protection of internal data in the vCenter Server, which may allow a remote attacker to disclose sensitive information. A malicious actor with administrative privileges on the vCenter appliance shell may exploit this issue to partially read arbitrary files containing sensitive data. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

The issue is related to the exposure of diagnostic information and controls through MBeans, which are also accessible through the authenticated Jolokia endpoint. This includes the Log4J2 MBean, which is not intended for non-administrative users. An authenticated attacker could exploit this to write arbitrary files to the filesystem, potentially leading to remote code execution.

The issue is related to insufficient comparison in the Apache NiFi data processing platform. An authenticated and authorized user can bypass connection URL validation using custom input formatting, potentially allowing a remote attacker to gain unauthorized access to protected information. The vulnerability affects several Processors and Controller Services that support JDBC and JNDI JMS access.

A Persistent Cross-site Scripting (XSS) issue can be carried out on certain pages, allowing an attacker to hijack a user's session and perform other attacks.

The Unica application exposes an API which accepts arbitrary XML input. By manipulating the given XML, an authenticated attacker with certain rights can successfully perform XML External Entity attacks (XXE) against the backend service.

A Persistent XSS issue can be exploited in a certain field, allowing an attacker to hijack a user's session and perform other attacks.

A Persistent Cross-site Scripting (XSS) issue can be exploited in a certain field of the Unica Platform, allowing an attacker to hijack a user's session and perform other attacks.

The JndiJmsConnectionFactoryProvider Controller Service, along with the ConsumeJMS and PublishJMS Processors, allow an authenticated and authorized user to configure URL and library properties that enable deserialization of untrusted data from a remote location. The resolution validates the JNDI URL and restricts locations to a set of allowed schemes.

The issue in Apache NiFi is related to the DBCPConnectionPool and HikariCPConnectionPool Controller Services, which allow an authenticated and authorized user to configure a Database URL with the H2 driver, enabling custom code execution. This can be exploited by a remote attacker to execute arbitrary code. Thousands of organizations are impacted by this issue. The resolution involves validating the Database URL and rejecting H2 JDBC locations.

The issue allows privilege escalation by a malicious local user due to the JMX management service being provided without authentication by default. Administrators are advised to take mitigation measures.

The issue is related to the use of a hard-coded cryptographic key in the Policy Manager software of Dell Secure Connect Gateway (SCG). An attacker with knowledge of the hard-coded sensitive information could potentially exploit this to login to the system and gain LDAP user privileges.

The issue is related to a Hard-coded Cryptographic Key, which could allow an attacker with knowledge of the hard-coded sensitive information to potentially exploit this vulnerability and gain admin privileges by logging into the system. An attacker could exploit this to elevate their privileges.

The issue is related to a hard-coded password vulnerability. An attacker with knowledge of the hard-coded credentials could exploit this to login to the system and gain admin privileges. The vulnerability is also associated with the use of a hard-coded cryptographic key, which could allow an attacker to elevate their privileges.

The issue is related to an Improper Control of Dynamically-Managed Code Resources vulnerability. This vulnerability allows authenticated developers to execute OS commands via a Groovy Sandbox Bypass. It may enable a remote attacker to execute arbitrary code.