Insecure Storage of Web Transfer Credentials in Progress WS_FTP Server
Progress Software WS_FTP Server versions prior to 2025.0.5 on Windows may write sensitive user credential and session data to a temporary file during file transfer operations.
Progress Software WS_FTP Server versions prior to 2025.0.5 on Windows may write sensitive user credential and session data to a temporary file during file transfer operations.
IBM MQ 9.2.0.0 through 9.2.0.44 LTS, 9.3.0.0 through 9.3.0.42 LTS, 9.4.0.0 through 9.4.0.26 LTS, 9.4.0.0 through 9.4.5.1 CD, and 10.0.0.0 through 10.0.0.5 LTS and CD is vulnerable to an XML external entity injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources.
IBM MQ 9.2.0.0 through 9.2.0.44 LTS, 9.3.0.0 through 9.3.0.42 LTS, 9.4.0.0 through 9.4.0.26 LTS, 9.4.0.0 through 9.4.5.1 CD, and 10.0.0.0 through 10.0.0.5 LTS and CD is vulnerable to an XML external entity injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources.
Out-of-bounds read in Microsoft Office PowerPoint allows an unauthorized attacker to disclose information over a network.
Use after free in Microsoft Office PowerPoint allows an unauthorized attacker to execute code over a network.
Use after free in Microsoft Office PowerPoint allows an unauthorized attacker to execute code over a network.
IBM MQ 9.2.0.0 through 9.2.0.44 LTS, 9.3.0.0 through 9.3.0.42 LTS, 9.4.0.0 through 9.4.0.26 LTS, 9.4.0.0 through 9.4.5.1 CD, and 10.0.0.0 through 10.0.0.5 LTS and CD could allow an authenticated attacker to execute arbitrary code by injecting malicious environment variables through transfer request metadata.
Buffer over-read in Microsoft Office allows an unauthorized attacker to disclose information over a network.
IBM MQ 9.2.0.0 through 9.2.0.44 LTS, 9.3.0.0 through 9.3.0.42 LTS, 9.4.0.0 through 9.4.0.26 LTS, 9.4.0.0 through 9.4.5.1 CD, and 10.0.0.0 through 10.0.0.5 LTS and CD stores potentially sensitive information in log files that could be read by a local user.
Heap-based buffer overflow in Microsoft Office Access allows an unauthorized attacker to execute code over a network.
Tanium addressed an improper access controls vulnerability in Enforce.
Heap-based buffer overflow in Microsoft Office Access allows an unauthorized attacker to execute code over a network.
A flaw was found in OpenShift Hive. The ClusterClaim controller assigns hive-claim-owner RBAC based on a user-controlled ClusterClaim.spec.namespace and only verifies ClusterPoolRef.ClaimName. A tenant can point a same-named claim at another tenant's ClusterDeployment and obtain get access to that cluster's admin kubeconfig and admin password secrets.
Camunda 7.24.0 before 7.24.14 and 7.23.0 before 7.23.17 contains an XML External Entity (XXE) injection vulnerability in the camunda-external-task-client's DomXmlDataFormat.defaultDocumentBuilderFactory(), which fails to disable external entity resolution when parsing object variables serialized with application/xml. An attacker able to write a process variable can trigger arbitrary file read and out-of-band outbound HTTP requests from every worker JVM that deserializes the variable, enabling exfiltration of credentials, service-account tokens, and private key material from network segments deeper than the engine itself.
Missing Authorization vulnerability in UX-themes Flatsome flatsome allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Flatsome: from n/a before 3.20.13.
Flagr before 1.2.5 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to access the flag management write API through an insecure default FLAGR_BASIC_AUTH_WHITELIST_PATHS including /api/v1/flags. Because basicAuth.whitelist() in pkg/config/middleware.go matches only path prefixes regardless of HTTP method, attackers can create, modify, enable, disable, and delete flags, variants, segments, constraints, and distributions.
Dolibarr ERP CRM through 24.0.3 contains a code injection vulnerability in Website::importWebSite() that allows website editors without PHP permission to execute code by importing templates. Attackers can import a template zip whose javascript.js.php contains PHP code, which the public javascript.js.php endpoint includes, executing code as the web server user.
BISHENG before 3.0.0 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to impersonate administrators by abusing a hard-coded default jwt_secret used by AuthJwt. Attackers can forge an HS256 token offline naming user_id 1 with the admin role, send it as access_token_cookie, and gain full administrative access to users, workspaces, knowledge bases and workflows.
Incorrect authorization in the credential handling for namespace-scoped issuers in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before 1.12.0 might allow an authenticated remote user with permission to create namespace-scoped issuers to obtain certificates, including subordinate CA certificates, from every AWS Private CA and certificate template reachable by the controller's own AWS identity or by any IAM role that identity can assume. This happens because a namespace-scoped issuer that supplies no credentials, or sets only a role, falls back to the controller's own identity. To remediate this issue, users should first update any namespace-scoped issuers that rely on the controller's identity to use their own credentials. Then, upgrade aws-privateca-issuer to version 1.12.0 or the AWS Private CA Connector for Kubernetes EKS add-on to version v1.12.0-eksbuild.1.
Incorrect authorization in the credential loading logic in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before 1.12.0 might allow an authenticated remote user with permission to create namespace-scoped issuers to obtain certificates, including subordinate CA certificates, signed by another namespace's AWS Private CA with that namespace's stored AWS credentials, via a namespace-scoped issuer that references a credentials Secret in that namespace. To remediate this issue, users should first copy any credentials Secret they intend a namespace-scoped issuer to use into that issuer's namespace and update the issuer's secretRef.namespace to match. Then, upgrade aws-privateca-issuer to version 1.12.0 or the AWS Private CA Connector for Kubernetes EKS add-on to version v1.12.0-eksbuild.1.