Aurelien Thirion

**Name of the Vulnerable Software and Affected Versions** AIL Framework (affected versions not specified) **Description** A server-side request forgery (SSRF) issue exists in the crawler submission functionality. A low-privileged authenticated user can submit arbitrary URLs for crawling due to insufficient validation of the destination host. This allows the crawler to make direct HTTP(S) requests to restricted addresses, such as loopback addresses, RFC1918 private networks, link-local addresses, and cloud metadata services like 169.254.169.254. Manual crawler tasks bypass the domain blacklist because they are assigned a non-zero priority, and IP literals are fetched directly instead of using a proxy. An attacker can use the server as a network pivot to access internal services. Since the crawler interface provides access to the resulting HTML, screenshots, and HAR data, the SSRF is non-blind, potentially leading to the disclosure of sensitive internal data, service information, or cloud instance credentials. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** AIL Framework (affected versions not specified) **Description** A reflected cross-site scripting issue exists in the '/tag/add tags' endpoint. When a tag operation fails, the application returns the error value as an HTML response via the `str(res[0])` function without proper output encoding. An attacker can exploit this by tricking an authenticated user into clicking a crafted link, allowing arbitrary JavaScript to execute in the victim's browser. This could enable the attacker to perform actions using the victim's session, access sensitive information, or modify data. The attack requires user interaction and does not necessarily require the attacker to have an account. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability. Restrict access to the '/tag/add tags' endpoint to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** AIL Project (affected versions not specified) **Description** A stored cross-site scripting issue exists in the translation controls for chat messages and forum posts. The system inserts message and post identifiers directly into inline JavaScript `onclick` handlers within the functions `translateMessageToPreferredLanguage()` and `translatePostToPreferredLanguage()`. While these values are HTML-template escaped, they are not safely encoded for use as JavaScript string literals inside an HTML attribute. An attacker can use a specially crafted identifier containing quotation marks or escape characters to terminate the string argument and inject arbitrary JavaScript. Since these values are stored, the malicious code executes in the victim's browser under the security origin of the AIL instance when they click the Translate to preferred language button. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** AIL Framework (affected versions not specified) **Description** A stored cross-site scripting issue exists in the crawler domain view. The application embeds crawled URLs directly into a JavaScript onclick handler used to display stored screenshots without proper encoding. An attacker can record a specially crafted URL in the crawler history to inject JavaScript syntax. When an authenticated analyst clicks the screenshot icon for the malicious URL, the script executes within the analyst's browser session. This could allow the attacker to access session information, modify content, or perform actions using the analyst's privileges. Exploitation requires the victim to interact with the affected screenshot entry. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** PlaywrightCapture (affected versions not specified) **Description** PlaywrightCapture stored configuration and runtime data as mutable class-level variables instead of instance-level variables. This allows multiple Capture objects within the same Python process to share state, including HTTP headers, cookies, browser storage, HTTP credentials, proxy configuration, user-agent settings, geolocation information, and captured request data. In concurrent or multi-user deployments, data from one capture can persist and be reused by others, potentially leading to the disclosure of authentication cookies, credentials, or browser storage. This may also allow requests to be executed using another capture's authentication context or proxy configuration, enabling unauthorized access to remote resources. **Recommendations** Initialize all capture-specific settings and request data as instance variables in the Capture constructor to ensure state isolation between operations.

**Name of the Vulnerable Software and Affected Versions** AIL Framework versions prior to commit 14c618fce4d1df02358717c48ea903706abecdf2 **Description** A path traversal issue exists in the PDF object handling. The `PDF.get filepath()` function constructs a file path by joining the configured PDF storage directory with a path derived from a PDF object identifier without verifying if the resolved path remains within the intended `PDF FOLDER` directory. An authenticated attacker could use relative traversal sequences or absolute path components via a crafted identifier to open files outside the storage directory, potentially leading to the disclosure of sensitive local data, credentials, or application configurations readable by the AIL process. **Recommendations** Update AIL Framework to the version containing commit 14c618fce4d1df02358717c48ea903706abecdf2.

**Name of the Vulnerable Software and Affected Versions** AIL (affected versions not specified) **Description** AIL failed to restrict repeated unsuccessful attempts to verify a two-factor authentication (OTP) code. An attacker who successfully completed the password authentication stage could submit an unlimited number of OTP guesses. This allows for brute-force guessing of a valid code to bypass the second authentication factor and gain unauthorized account access. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** AIL Framework versions prior to commit 0041456af25da0cdea1c1c4624e46baff2731d8f **Description** A path traversal issue allows an authenticated user to supply crafted object identifiers through the investigation workflow, causing file paths to resolve outside the intended image, favicon, or screenshot storage directories. This occurs because user-controlled path components are joined with application storage paths without verifying that the resolved path remains within the expected directory. Consequently, an attacker can download and read arbitrary files accessible to the AIL process via the affected download functionality, which may include these files in a generated archive. **Recommendations** Update to the release containing commit 0041456af25da0cdea1c1c4624e46baff2731d8f.

**Name of the Vulnerable Software and Affected Versions** AIL framework (affected versions not specified) **Description** A path traversal issue exists in the '/objects/item/diff' endpoint. The endpoint accepts item identifiers via the `s1` and `s2` query parameters and attempts to retrieve and compare item contents without verifying that the referenced items are valid AIL objects. An authenticated user can use path traversal sequences in these parameters to read gzip-compressed files accessible to the AIL process, potentially leading to the unauthorized disclosure of local file contents compatible with the expected gzip format. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.