CVE Vulnerability Catalog

IBM i versions 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to execute arbitrary code or obtain sensitive information due to improper authentication.

IBM i versions 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to obtain sensitive information due to improper authentication.

The Signify Philips Hue Bridge Pro firmware embeds a Mosquitto MQTT broker service that listens on all network interfaces without authentication. An unauthenticated attacker with network access to the MQTT service on a vulnerable system can read data and control connected lights. Fixed in 1.77.2071318010.

Trigger.dev before version 4.5.2 contains a vulnerability in addGoogleStrategy() that passes a Google profile email to findOrCreateGoogleUser() without requiring Google's email_verified assertion. When an existing email-matched account exists, an attacker can take over the account using an unverified matching email from their own Google profile.

Trigger.dev from version 3.3.8 to 4.5.6 contains a vulnerability in the PUT /api/v1/runs/:runId/metadata endpoint, where operation.key values are passed to new JSONHeroPath(operation.key).set() without rejecting dangerous constructor and prototype path segments. A caller with a normal environment API key can pollute Object.prototype in the shared webapp process, corrupting Prisma queries and Prometheus labels, breaking other tenants' worker authentication, and causing a process-wide denial of service.

Flyto2 Core before version 2.28.0 contains a server-side request forgery guard bypass vulnerability that allows attackers to reach internal services by supplying URLs using the unblocked IPv6 address `::` which the kernel routes to loopback identically to `0.0.0.0`. Attackers can submit requests or trigger 302 redirects to bypass the private IP range and blocked hostname checks in is_private_ip(), reaching services bound to IPv6 loopback across the http.get, http.request, and http.batch modules.

Kibana contains a Relative Path Traversal (CWE-23) vulnerability that can lead to unauthorized deletion of Kibana resources. Kibana Fleet accepted a user-supplied identifier for a Fleet Server host configuration without rejecting relative traversal sequences. The identifier is stored and later incorporated into the request when that configuration is removed.

Kibana contains a Missing Authorization (CWE-862) vulnerability that can lead to cross-space information disclosure and unauthorized data modification. Kibana Machine Learning carries out its Elasticsearch operations with elevated internal permissions and relies on a per-request space filter to keep ML data separated. Part of the ML functionality did not apply that filter, so operations from one space were carried out against ML data of every space.

The Elastic Security capability that suggests existing field values while a user authors endpoint policy artifacts queries Elastic Defend event data with Kibana's internal Elasticsearch account instead of the requesting user's account. Only Kibana feature privileges are verified, not the caller's Elasticsearch index privileges. An authenticated user with Elastic Security feature privileges but no read access to Elastic Defend event indices can retrieve field values, including process command line arguments, which commonly contain tokens, credentials, and other sensitive operational detail.

A lower privileged user who holds only the privilege to read agent policies can read the entire configuration of a configured Fleet proxy. This would normally require the Fleet privilege to read settings. The proxy configuration possibly contains proxy authentication credentials and private key material that they should not be authorized to view.

The state that Kibana stores for an Observability Onboarding flow is not bound to the user who created the flow, and the routes that read and update that state do not verify ownership. An authenticated user with only generic read access to the space can discover other users' onboarding flows, read their state, and write arbitrary progress data. A tampered flow can also cause the owner's onboarding view to fail with a server error.

Missing Authorization in Kibana can lead to unauthorized execution of Osquery and Elastic Defend response actions on managed hosts. A Kibana user who can author and evaluate Elastic Security detection rules can trigger response actions on enrolled agents without the required privileges.

Cross-Site Request Forgery in Kibana can lead to privilege escalation. A user allowed to create visualizations can save a crafted Vega visualization that, when opened by another user, triggers authenticated requests in the victim's session.

Kibana Agent Builder determines ownership of a private agent by comparing a stable user identifier when available, otherwise falling back to username comparison. Usernames are not unique across Elasticsearch authentication realms, so two distinct principals with the same username are treated as the same owner.

The native inference process in Elasticsearch for evaluating uploaded ML models accepts a model operation that computes a memory address from an offset without validating bounds. A user with privileges to upload and deploy models can craft a model that reads/writes memory outside the intended allocation.

Observable Discrepancy in Kibana Fleet leads to information disclosure. Fleet removes the Elasticsearch API key value from agent listing responses, but accepts caller-supplied filters evaluated with Kibana's internal privileges, creating a side channel to reconstruct the full API key.

Incorrect Authorization in Kibana Fleet can lead to privilege escalation. Fleet restricts some callers to managing integration policies for one specific integration, but when updating a policy, the restriction is evaluated against the stored integration rather than the replacement integration.

Authorization Bypass Through User-Controlled Key in Kibana allows unauthorized cross-space access. A user can access inference output from a trained model in another space without authorization, and can also stop or alter resources of an active model deployment.

Open WebUI from 0.9.5 before 0.10.0 allows any authenticated user to overwrite message content in a channel they do not belong to (including private and DM channels) by sending a chat completion request with a channel:-prefixed chat_id and a target message_id. Fixed in version 0.10.0.

wetty prior to version 3.0.4 decodes a base64 filename from the file-download escape sequence and interpolates it raw into a Toastify HTML string. Any output rendered by the victim containing \x1b[5i...:...\x1b[4i can run script in the wetty origin and type attacker-chosen keystrokes into the victim's SSH session.