
Ozon
Ozon



Ozon

Texwipe, an ITW company, is the worldwide leader in supplying contamination control and cleaning products for critical clean environments in the manufacture of pharmaceuticals, biologics, medical devices, optics, aerospace/aviation, semiconductors, microelectronics, and compounding pharmacies. At Texwipe, we are driven by a commitment to continuous innovation and excellence in customer service to provide you products with the highest levels of cleanliness and consistency. All Texwipe products are supported by the most advanced testing technologies and quality control standards in the industry that we helped to launch. Texwipe's broad product line for contamination control includes a complete array of cleanroom consumables such as: • Wipers • Swabs • Mops and Buckets • Cleaning alcohol solutions • Disinfectants • Stationery and labels • Adhesive tapes • Sticky mats Texwipe also develops custom products to address specific customer application needs. We are working with the leaders in technology-driven industries to apply our expertise in ever-expanding ways. If you are looking for the best in the business, contact us today at [email protected], (800) TEXWIPE ((800) 839-9573), or view our website at TEXWIPE. Show more Show less
Security & Compliance Standards Overview












No incidents recorded for Ozon in 2025.
No incidents recorded for Texwipe in 2025.
Ozon cyber incidents detection timeline including parent company and subsidiaries
Texwipe cyber incidents detection timeline including parent company and subsidiaries
Last 3 Security & Risk Events by Company
FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.
Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.
Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.
Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.
The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.