Vulnerabilidades

*** Pendiente de traducción *** Tinacms is a Git-backed headless content management system with support for visual editing. Sites being built with @tinacms/cli >= 1.0.0 &&

*** Pendiente de traducción *** IBM API Connect 10.0.0.0 through 10.0.5.0, 10.0.1.0 through 10.0.1.7, and 2018.4.1.0 through 2018.4.1.20 is vulnerable to External Service Interaction attack, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability to induce the application to perform server-side DNS lookups or HTTP requests to arbitrary domain names. By submitting suitable payloads, an attacker can cause the application server to attack other systems that it can interact with. IBM X-Force ID: 230264.

*** Pendiente de traducción *** A timing based side channel exists in the OpenSSL RSA Decryption implementation<br /> which could be sufficient to recover a plaintext across a network in a<br /> Bleichenbacher style attack. To achieve a successful decryption an attacker<br /> would have to be able to send a very large number of trial messages for<br /> decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5,<br /> RSA-OEAP and RSASVE.<br /> <br /> For example, in a TLS connection, RSA is commonly used by a client to send an<br /> encrypted pre-master secret to the server. An attacker that had observed a<br /> genuine connection between a client and a server could use this flaw to send<br /> trial messages to the server and record the time taken to process them. After a<br /> sufficiently large number of messages the attacker could recover the pre-master<br /> secret used for the original connection and thus be able to decrypt the<br /> application data sent over that connection.

*** Pendiente de traducción *** The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and<br /> decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data.<br /> If the function succeeds then the "name_out", "header" and "data" arguments are<br /> populated with pointers to buffers containing the relevant decoded data. The<br /> caller is responsible for freeing those buffers. It is possible to construct a<br /> PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex()<br /> will return a failure code but will populate the header argument with a pointer<br /> to a buffer that has already been freed. If the caller also frees this buffer<br /> then a double free will occur. This will most likely lead to a crash. This<br /> could be exploited by an attacker who has the ability to supply malicious PEM<br /> files for parsing to achieve a denial of service attack.<br /> <br /> The functions PEM_read_bio() and PEM_read() are simple wrappers around<br /> PEM_read_bio_ex() and therefore these functions are also directly affected.<br /> <br /> These functions are also called indirectly by a number of other OpenSSL<br /> functions including PEM_X509_INFO_read_bio_ex() and<br /> SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal<br /> uses of these functions are not vulnerable because the caller does not free the<br /> header argument if PEM_read_bio_ex() returns a failure code. These locations<br /> include the PEM_read_bio_TYPE() functions as well as the decoders introduced in<br /> OpenSSL 3.0.<br /> <br /> The OpenSSL asn1parse command line application is also impacted by this issue.

*** Pendiente de traducción *** Privilege escalation in the MSI repair functionality in Caphyon Advanced Installer 20.0 and below allows attackers to access and manipulate system files.

*** Pendiente de traducción *** IBM Sterling External Authentication Server 6.1.0 and IBM Sterling Secure Proxy 6.0.3 uses weaker than expected cryptographic algorithms during installation that could allow a local attacker to decrypt sensitive information. IBM X-Force ID: 231373.

*** Pendiente de traducción *** SQL Injection vulnerability in Future-Depth Institutional Management Website (IMS) 1.0, allows attackers to execute arbitrary commands via the ad parameter to /admin_area/login_transfer.php.

*** Pendiente de traducción *** File upload vulnerability in Future-Depth Institutional Management Website (IMS) 1.0, allows unauthorized attackers to directly upload malicious files to the courseimg directory.

*** Pendiente de traducción *** Cross-site scripting (XSS) vulnerability in EyouCMS v1.6.0 allows attackers to execute arbitrary code via the home page description on the basic information page.

*** Pendiente de traducción *** HashiCorp Boundary from 0.10.0 through 0.11.2 contain an issue where when using a PKI-based worker with a Key Management Service (KMS) defined in the configuration file, new credentials created after an automatic rotation may not have been encrypted via the intended KMS. This would result in the credentials being stored in plaintext on the Boundary PKI worker’s disk.<br /> <br /> This issue is fixed in version 0.12.0.

*** Pendiente de traducción *** IBM Infosphere Information Server 11.7 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 245423.

*** Pendiente de traducción *** Wings is Pterodactyl&amp;#39;s server control plane. Affected versions are subject to a vulnerability which can be used to create new files and directory structures on the host system that previously did not exist, potentially allowing attackers to change their resource allocations, promote their containers to privileged mode, or potentially add ssh authorized keys to allow the attacker access to a remote shell on the target machine. In order to use this exploit, an attacker must have an existing "server" allocated and controlled by the Wings Daemon. This vulnerability has been resolved in version `v1.11.3` of the Wings Daemon, and has been back-ported to the 1.7 release series in `v1.7.3`. Anyone running `v1.11.x` should upgrade to `v1.11.3` and anyone running `v1.7.x` should upgrade to `v1.7.3`. There are no known workarounds for this vulnerability.<br /> <br /> ### Workarounds<br /> <br /> None at this time. <br /> <br /> <br /> <br />