Vulnerabilities

Dell NativeEdge, version(s) 2.1.0.0, contain(s) a Creation of Temporary File With Insecure Permissions vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to Information disclosure.

Dell ECS, version(s) prior to ECS 3.8.1.3, contain(s) an Authentication Bypass by Capture-replay vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Session theft.

Dell NativeEdge, version(s) 2.1.0.0, contain(s) an Exposure of Sensitive Information Through Metadata vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to Information disclosure.

Dell SupportAssist for Home PCs versions 4.6.1 and prior and Dell SupportAssist for Business PCs versions 4.5.0 and prior, contain a symbolic link (symlink) attack vulnerability in the software remediation component. A low-privileged authenticated user could potentially exploit this vulnerability, gaining privileges escalation, leading to arbitrary deletion of files and folders from the system.

IBM AIX 7.2, 7.3, VIOS 3.1, and 4.1<br /> <br /> <br /> <br /> could allow a non-privileged local user to exploit a vulnerability in the TCP/IP kernel extension to cause a denial of service.

Dell NativeEdge, version(s) 2.1.0.0, contain(s) an Execution with Unnecessary Privileges vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Elevation of privileges.

IBM AIX 7.2, 7.3, VIOS 3.1, and 4.1<br /> <br /> could allow a non-privileged local user to exploit a vulnerability in the AIX perfstat kernel extension to cause a denial of service.

An issue was discovered in GitLab CE/EE affecting all versions before 17.6.0 in which users were unaware that files uploaded to comments on confidential issues and epics of public projects could be accessed without authentication via a direct link to the uploaded file URL.

IBM Engineering Lifecycle Optimization - Engineering Insights 7.0.2 and 7.0.3 uses a web link with untrusted references to an external site. A remote attacker could exploit this vulnerability to expose sensitive information or perform unauthorized actions on the victims’ web browser.

IBM Engineering Lifecycle Optimization - Engineering Insights 7.0.2 and 7.0.3 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system.

Improper Neutralization of Special Elements used in an SQL Command (&amp;#39;SQL Injection&amp;#39;) vulnerability in Arne Informatics Piramit Automation allows Blind SQL Injection.This issue affects Piramit Automation: before 27.09.2024.

The ObjectSerializationDecoder in Apache MINA uses Java’s native deserialization protocol to process<br /> incoming serialized data but lacks the necessary security checks and defenses. This vulnerability allows<br /> attackers to exploit the deserialization process by sending specially crafted malicious serialized data,<br /> potentially leading to remote code execution (RCE) attacks.<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> This issue affects MINA core versions 2.0.X, 2.1.X and 2.2.X, and will be fixed by the releases 2.0.27, 2.1.10 and 2.2.4.<br /> <br /> <br /> <br /> <br /> <br /> It&amp;#39;s also important to note that an application using MINA core library will only be affected if the IoBuffer#getObject() method is called, and this specific method is potentially called when adding a ProtocolCodecFilter instance using the ObjectSerializationCodecFactory class in the filter chain. If your application is specifically using those classes, you have to upgrade to the latest version of MINA core library.<br /> <br /> <br /> <br /> <br /> Upgrading will  not be enough: you also need to explicitly allow the classes the decoder will accept in the ObjectSerializationDecoder instance, using one of the three new methods:<br /> <br /> <br /> <br /> <br /> /**<br /> <br />      * Accept class names where the supplied ClassNameMatcher matches for<br /> <br /> * deserialization, unless they are otherwise rejected.<br /> <br /> *<br /> <br /> * @param classNameMatcher the matcher to use<br /> <br /> */<br /> <br /> public void accept(ClassNameMatcher classNameMatcher)<br /> <br /> <br /> <br /> <br /> /**<br /> <br /> * Accept class names that match the supplied pattern for<br /> <br /> * deserialization, unless they are otherwise rejected.<br /> <br /> *<br /> <br /> * @param pattern standard Java regexp<br /> <br /> */<br /> <br /> public void accept(Pattern pattern) <br /> <br /> <br /> <br /> <br /> <br /> /**<br /> <br /> * Accept the wildcard specified classes for deserialization,<br /> <br /> * unless they are otherwise rejected.<br /> <br /> *<br /> <br /> * @param patterns Wildcard file name patterns as defined by<br /> <br /> * {@link org.apache.commons.io.FilenameUtils#wildcardMatch(String, String) FilenameUtils.wildcardMatch}<br /> <br /> */<br /> <br /> public void accept(String... patterns)<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> By default, the decoder will reject *all* classes that will be present in the incoming data.<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> Note: The FtpServer, SSHd and Vysper sub-project are not affected by this issue.