Vulnerabilidades

*** Pendiente de traducción *** Apache Log4cxx&amp;#39;s XMLLayout https://logging.apache.org/log4cxx/1.7.0/classlog4cxx_1_1xml_1_1XMLLayout.html , in versions before 1.7.0, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets in log messages, NDC, and MDC property keys and values, producing invalid XML output. Conforming XML parsers must reject such documents with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records.<br /> <br /> An attacker who can influence logged data can exploit this to suppress individual log records, impairing audit trails and detection of malicious activity.<br /> <br /> Users are advised to upgrade to Apache Log4cxx 1.7.0, which fixes this issue.

*** Pendiente de traducción *** Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the OIDC callback handler issues a full JWT token without checking whether the matched user has TOTP two-factor authentication enabled. When a local user with TOTP enrolled is matched via the OIDC email fallback mechanism, the second factor is completely skipped. This vulnerability is fixed in 2.3.0.

*** Pendiente de traducción *** Apache Log4j Core&amp;#39;s Rfc5424Layout https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout , in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes.<br /> <br /> Two distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly:<br /> <br /> * The newLineEscape attribute was silently renamed, causing newline escaping to stop working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output.<br /> * The useTlsMessageFormat attribute was silently renamed, causing users of TLS framing (RFC 5425) to be silently downgraded to unframed TCP (RFC 6587), without newline escaping.<br /> <br /> <br /> Users of the SyslogAppender are not affected, as its configuration attributes were not modified.<br /> <br /> Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.

*** Pendiente de traducción *** The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records.<br /> <br /> Two groups of users are affected:<br /> <br /> * Those using Log4j1XmlLayout directly in a Log4j Core 2 configuration file.<br /> * Those using the Log4j 1 configuration compatibility layer with org.apache.log4j.xml.XMLLayout specified as the layout class.<br /> <br /> <br /> Users are advised to upgrade to Apache Log4j 1-to-Log4j 2 bridge version 2.25.4, which corrects this issue.<br /> <br /> Note: The Apache Log4j 1-to-Log4j 2 bridge is deprecated and will not be present in Log4j 3. Users are encouraged to consult the Log4j 1 to Log4j 2 migration guide https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html , and specifically the section on eliminating reliance on the bridge.

*** Pendiente de traducción *** Apache Log4j Core&amp;#39;s XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters.<br /> <br /> The impact depends on the StAX implementation in use:<br /> <br /> * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records.<br /> * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j&amp;#39;s internal status logger.<br /> <br /> <br /> Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.

*** Pendiente de traducción *** Apache Log4j&amp;#39;s JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.<br /> <br /> An attacker can exploit this issue only if both of the following conditions are met:<br /> <br /> * The application uses JsonTemplateLayout.<br /> * The application logs a MapMessage containing an attacker-controlled floating-point value.<br /> <br /> <br /> Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.

*** Pendiente de traducción *** An issue was discovered in BMC Control-M/MFT 9.0.20 through 9.0.22. A set of default debug user credentials is hardcoded in cleartext within the application package. If left unchanged, these credentials can be easily obtained and may allow unauthorized access to the MFT API debug interface.

*** Pendiente de traducción *** CouchCMS contains a privilege escalation vulnerability that allows authenticated Admin-level users to create SuperAdmin accounts by tampering with the f_k_levels_list parameter in user creation requests. Attackers can modify the parameter value from 4 to 10 in the HTTP request body to bypass authorization validation and gain full application control, circumventing restrictions on SuperAdmin account creation and privilege assignment.

*** Pendiente de traducción *** HDF5 is software for managing data. In 1.14.1-2 and earlier, an attacker who can control an h5 file parsed by HDF5 can trigger a write-based heap buffer overflow condition in the H5T__ref_mem_setnull method. This can lead to a denial-of-service condition, and potentially further issues such as remote code execution depending on the practical exploitability of the heap overflow against modern operating systems.

*** Pendiente de traducción *** The fix for CVE-2025-68161 https://logging.apache.org/security.html#CVE-2025-68161 was incomplete: it addressed hostname verification only when enabled via the log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName system property, but not when configured through the verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName attribute of the element.<br /> <br /> Although the verifyHostName configuration attribute was introduced in Log4j Core 2.12.0, it was silently ignored in all versions through 2.25.3, leaving TLS connections vulnerable to interception regardless of the configured value.<br /> <br /> A network-based attacker may be able to perform a man-in-the-middle attack when all of the following conditions are met:<br /> <br /> * An SMTP, Socket, or Syslog appender is in use.<br /> * TLS is configured via a nested element.<br /> * The attacker can present a certificate issued by a CA trusted by the appender&amp;#39;s configured trust store, or by the default Java trust store if none is configured.<br /> This issue does not affect users of the HTTP appender, which uses a separate verifyHostname https://logging.apache.org/log4j/2.x/manual/appenders/network.html#HttpAppender-attr-verifyHostName attribute that was not subject to this bug and verifies host names by default.<br /> <br /> Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.

*** Pendiente de traducción *** A SQL injection vulnerability was found in the scheduleSubList.php file of itsourcecode Online Student Enrollment System v1.0. The reason for this issue is that the &amp;#39;subjcode&amp;#39; parameter is directly embedded into the SQL query via string interpolation without any sanitization or validation.

*** Pendiente de traducción *** SourceCodester Engineers Online Portal v1.0 is vulnerable to SQL Injection in update_password.php via the new_password parameter.