CVE Vulnerability Catalog

In Zammad prior to 7.1.2, a security filter protecting the AI Agent configuration can be bypassed by entering specially crafted text into one of an AI Agent's fields. An administrator with permission to create or edit AI Agents could exploit this to run arbitrary commands on the server hosting Zammad, potentially reading, modifying, or destroying all data stored on that server. No interaction from other users is needed; the malicious code runs automatically the next time the affected AI Agent processes a ticket. This issue is fixed in version 7.1.2.

Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, the legacy destroy_form action on AttachmentsController deletes UploadCache Store records based solely on a user-supplied form_id without verifying that the requesting user owns those records. An authenticated attacker who learns another user's pending-upload UUID can silently remove temporary file uploads before the victim submits their ticket or article. This issue is fixed in version 7.1.2.

In Zammad versions 7.0.2 and 7.1.0, session management for websocket and long-polling connections is susceptible to a path traversal attack. Session identifiers supplied by the client are insufficiently validated before being used to construct internal file paths. When the file-based session store is active (the default configuration), an authenticated attacker can manipulate the session identifier to reference locations outside the intended storage directory, leading to the deletion of arbitrary files and directories on the server. Exploitation requires only a low-privilege authenticated session and a single crafted request. Instances configured to use the Redis-based session store are not affected. This issue is fixed in versions 7.0.3 and 7.1.1.

Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2 and 7.1.0, zammad's HTML sanitizer (HtmlSanitizer::Strict) blocks external URLs in to prevent remote content loading, but the srcset attribute, also allowlisted for , is not subject to the same check. This oversight allows an attacker to embed arbitrary external URLs in the srcset attribute just by sending an e-mail, effectively bypassing the external content protection. When an agent views the ticket containing the malicious srcset, the browser will silently load the attacker-controlled URL, resulting in the leakage of the agent's IP address, User-Agent, Referer, and the exact time the ticket was viewed. HtmlSanitizer::Strict got extended to block external URLs in the srcset attribute of tags. This was done to prevent tracking pixels and external content loading, which could compromise user privacy. This issue is fixed in versions 7.0.2 and 7.1.0.

Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2, during federated authentication (OAuth/OIDC/SAML), a profile image URL from the external identity provider is fetched without verifying the target address. An actor who controls their profile at a connected provider may cause the server to connect to internal network locations. Response timing and error patterns differ between reachable and unreachable targets, allowing internal service probing. Worker processes may be blocked for several seconds per request. Requires a configured external authentication provider where the actor can modify their profile image URL. This issue is fixed in version 7.0.2.

In Zammad prior to versions 7.0.2 and 7.1.0, there is a lack of validation within the authorization cascade. Under specific conditions, the granular restrictions of the access key are overridden by the latent authorization authority of the parent account, nullifying the intended separation of functional areas and resulting in uncontrolled expansion of administrative discretion. An attacker can create new administrator accounts despite token restrictions, gaining full access to all system data (tickets, customers, configuration) and complete control of the Zammad instance. This issue is fixed in versions 7.0.2 and 7.1.0.

Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2, vulnerability in Zammad's HTML sanitization allows injection of specific HTML elements into ticket bodies. When another user views the crafted ticket, the injected element can trigger a logout request, terminating the viewer's session. This vulnerability is fixed in 7.0.2.

In Zammad prior to version 7.0.1, a low-privilege authenticated user may inject arbitrary HTML markup, including JavaScript event handlers, into a ticket title via the standard ticket creation workflow. The title is persisted without sanitization. This issue is fixed in version 7.0.1.

Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2, an authorization bypass vulnerability was found that allows an authenticated agent to read knowledge base answer content they should not be able to access. The vulnerable GraphQL mutation is meant to transform a knowledge base answer suggestion so it can be inserted into the ticket editor, but it only checks if the user has the ticket.agent permission. Checking the authorization to the knowledge base answer itself is missing. This vulnerability is fixed in 7.0.2.

Prior to 7.0.2, Zammad has a broken access control vulnerability in its GraphQL API. An authenticated user can read another user's taskbar item data by supplying the target user's taskbar identifier, potentially exposing auto-saved ticket drafts.

In Zammad prior to version 7.0.2, in inbound PGP email processing, the return value of the gpg verification call was silently discarded. Regardless of whether gpg reported a valid, invalid, or missing signature, the handler unconditionally wrote sign: { success: true, comment: "Good signature" } to the article's security preferences. Any sender could tamper with the body of a multipart/signed PGP email, or craft a message with an entirely fabricated or mismatched signature, and Zammad would display it to the recipient as cryptographically verified with a "Good signature" label. Users and agents relying on Zammad's signature indicator to confirm message authenticity and integrity would be misled into trusting modified or forged content. The vulnerability affects all inbound PGP-signed emails processed while the PGP integration is enabled. This issue is fixed in version 7.0.2.

Prior to 7.0.2, any authenticated agent in Zammad can view titles, statuses, labels, and URLs of GitHub/GitLab issues attached to any ticket by querying ticket IDs. This breaks ticket isolation boundaries between agents.

In Zammad prior to version 7.0.2, an unauthenticated request to POST /api/v1/import/otrs/import_check blocks a Zammad request worker for roughly two minutes. The import_check and import_status actions are missing the setup_done_response guard that other actions in the same controller carry, so they execute on fully set-up production instances. The action enters a retry loop against a blank OTRS endpoint, sleeping for 30 s + 45 s between attempts. An unauthenticated remote attacker denies service to a production Zammad instance. Each request costs almost nothing and forces ~115 seconds of server-side blocking. A few requests per second saturate the Puma worker pool. This issue is fixed in version 7.0.2.

A security flaw has been discovered in zhistaredu StarTraining up to 3.8.1. The affected element is an unknown function of the file SecurityConfig.java of the component api-docs Endpoint. Performing a manipulation results in missing authentication. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks.

Vulnerability in StarTraining up to 3.8.1 in the anonymous function of /druid/index.html of the Druid Console component. Missing authentication allows remote attack. Exploit is publicly available.

Vulnerability in StarTraining up to 3.8.1 in the UserLoginService.createToken function of application.yml in the JWT Token Handler component. Manipulation of user_id/company_id causes use of hard-coded password. Remote attack, public exploit.

Vulnerability in Zhonglun CloudPos up to 3.0.1.76 in the OpenLocalBrowser function of ZlPos/ZlPos/Bizlogic/JSBridge.cs in the JSBridge component. Manipulation of the url argument leads to code injection. Remote attack, public exploit.

Missing Authorization in the askpass escape code handler in kitty from 0.25.0 before 0.49.0 allows a local user other than the one running the terminal to obtain text typed into a prompt displayed by kitty. The handle_remote_askpass() function opens the POSIX shared memory object named in the escape code and writes the user's answer back without verifying ownership or permissions. An attacker can create such an object, cause the victim's kitty to render a prompt of their choosing, and read the typed secret afterwards.

Use After Free vulnerability in the drag and drop protocol in kitty from 0.47.0 before 0.49.0 allows a program writing to the terminal to cause the terminal to read from and write to freed heap memory. The bug occurs in drag_remote_file_data() in kitty/dnd.c, where a pointer to an array is used after it has been freed by helper functions.

A vulnerability in golang.org/x/playground allows a malicious txtar file to escape the intended execution context and force arbitrary writes to the playground host's trusted filesystem. Additionally, one of the paths to invoke 'go vet' did not correctly restrict the execution environment, allowing a read of an environment configuration file from the host's $HOME. Together, these can lead to remote code execution on the playground host.