Historial de interrupciones de Inline Manual

1. 31 de julio de 2026 a las 11:27 UTCinvestigating

   Somos conscientes de la vulnerabilidad revelada recientemente CVE-2026-66066 y la tratamos seriamente. Nuestros sistemas de producción ya han sido reparados. Actualmente estamos realizando un examen forense exhaustivo de los registros pertinentes para confirmar si hubo algún intento de explotar la vulnerabilidad antes de que se aplicara el parche. En esta etapa, no hemos encontrado ninguna prueba de que Inline Manual fue afectado. Continuamos la investigación como precaución y compartiremos otra actualización una vez que el examen esté completo. [CVE-2026-66066] Posible ejecución de archivos arbitrarios y código remoto en procesamiento de variantes Active Storage - https://discuss.rubyonrails.org/t/cve-2026-66066-possible-arbitrary-file-read-and-remote-code-execution-in-active-storage-variant-processing/91432

2. 31 de julio de 2026 a las 19:08 UTCinvestigating

   Continuamos revisando nuestros registros para cualquier signo de que CVE-2026-66066 fue explotado antes de que nuestros sistemas fueran parcheados. Hasta ahora, no hemos encontrado evidencia de actividad maliciosa relacionada con esta vulnerabilidad. Nuestra respuesta rápida parece haber impedido cualquier explotación, y también hemos rotado todas las claves secretas afectadas como precaución adicional. Es importante, incluso si un atacante hubiera intentado explotar esta vulnerabilidad, no les habría dado acceso a los datos del cliente. Hemos confirmado esto basado en cómo el componente afectado está aislado dentro de nuestra infraestructura. Seguiremos revisando los registros y monitoreando cualquier actividad sospechosa durante el fin de semana. Publicaremos otra actualización antes si identificamos algo relevante, o para el lunes 3 de agosto a más tardar si no hay nuevos hallazgos.

3. 5 de agosto de 2026 a las 21:13 UTCresolved

   Resueltos - ninguna prueba de explotación Hemos completado nuestra investigación sobre el impacto potencial del CVE-2026-66066. Adoptamos un enfoque deliberadamente minucioso y fuimos más allá de nuestro proceso de examen estándar para asegurarnos de que habíamos examinado todas las fuentes pertinentes de información. Esto incluía: - Patear los sistemas afectados inmediatamente - Revisión de los registros de aplicaciones, infraestructuras y acceso correspondientes al período pertinente - Búsqueda de indicadores y patrones conocidos asociados con la explotación - Investigar solicitudes y actividades inusuales en mayor detalle - Rotating all potentially affected secret keys as a precaution - Continuación de la vigilancia después de la finalización del examen inicial - Verificar que el componente afectado no pudo proporcionar acceso a los datos del cliente Después de completar este trabajo, hemos encontrado cero pruebas de que la vulnerabilidad fue explotada o que Inline Manual fue afectado. Por lo tanto, estamos marcando este incidente como resuelto. Seguiremos siguiendo nuestros procesos normales de vigilancia de la seguridad y tomaremos nuevas medidas si se dispone de información nueva. Gracias. Marek y el equipo

Traducido automáticamente desde la actualización oficial del incidente.

1. 8 de octubre de 2024 a las 3:51 UTCinvestigating

   We are currently experiencing technical difficulties with our main website, inlinemanual.com. Our team is actively working to resolve the issue as quickly as possible, and we will provide updates as we have more information. In the meantime, we want to reassure you that our platform, app.inlinemanual.com, is fully operational and unaffected by this outage. You can continue to access all your sites, content, and features without any interruption. We apologize for any inconvenience this may cause and appreciate your patience and understanding as we work to restore our main website. If you have any questions or need assistance, please feel free to contact our support team at [email protected].

2. 8 de octubre de 2024 a las 4:00 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 8 de octubre de 2024 a las 4:08 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 8 de octubre de 2024 a las 4:29 UTCresolved

   This incident has been resolved.

1. 30 de marzo de 2024 a las 11:10 UTCinvestigating

   We're following the evolution of the situation around CVE-2024-3094 - https://nvd.nist.gov/vuln/detail/CVE-2024-3094 Our Engineering and Security teams are currently investigating if the CVE-2024-3094 incident applies to any of our service resources.

2. 30 de marzo de 2024 a las 12:28 UTCresolved

   This incident has been resolved. After a thorough investigation we conclude that our systems were not affected by the CVE-2024-3094 and the specified library versions.

1. 5 de diciembre de 2023 a las 10:53 UTCinvestigating

   Authoring Tool is currently unavailable. We are actively investigating the issue and working to restore access as soon as possible. Thank you for your understanding and patience.

2. 5 de diciembre de 2023 a las 10:54 UTCidentified

   We have identified the issue affecting the Authoring Tool and are diligently working on a fix. We expect to restore full functionality soon.

3. 5 de diciembre de 2023 a las 11:03 UTCmonitoring

   The issue with the Authoring Tool has been resolved and we are now closely monitoring the system for stability. Thank you for your patience, and we apologize for any inconvenience caused. Please feel free to resume using the tool.

4. 5 de diciembre de 2023 a las 17:23 UTCresolved

   This incident has been resolved.

1. 11 de enero de 2023 a las 20:48 UTCinvestigating

   We are experiencing a degraded performance on one of our parts of the Inline Manual Portal - app.inlinemanual.com. Affected areas: - People Tab - latest profiles and updates are not showing. - Various operations on People profiles are not working through the Portal. This does not affect your users' experience, as their progress is still being appropriately stored and processed without any delay.

2. 11 de enero de 2023 a las 21:50 UTCidentified

   We have identified the issue and are working on a fix.

3. 11 de enero de 2023 a las 22:04 UTCmonitoring

   Issue has been fixed. Sync jobs across all analytics servers are running as expected. The deletion and other Profile actions are working. The Profiles are being re-synchronised. We are monitoring the re-sync process as it might take several hours to update affected profiles fully and for any recurrence of issues. We have confirmed that this did not impact the end-users' experience and only impacted the Inline Manual's Portal UI, where we display Profiles.

4. 25 de enero de 2023 a las 17:47 UTCresolved

   We have been following the data consistency thoroughly throughout the past few weeks. This incident has been resolved.

1. 16 de diciembre de 2021 a las 10:35 UTCmonitoring

   Incident ongoing since December 11th. We're following the evolution of the situation around CVE-2021-45046. Our Engineering and Security teams started to work on log4j incident on December 10th in the morning EU time and updated, mitigated or removed the vulnerable log4j packages from our environment. No misuse has been detected and active threat hunting continues. Our mitigation actions: - Updated log4j where possible - Scanned logs retrospectively one month back for various scenarios - Our security team is still actively hunting for signs of exploitation The service affected is not directly accessible through internet. It sits within our private network. The request can be made through an API which goes through application first, not passing any headers and it correctly sanitizes all user entered content. This has been verified and confirmed. The service itself logs only minimum information, none of the user entered content makes it through to the logs. The attacker would need to be logged in to Inline Manual Portal or have API Access Tokens to be able to communicate indirectly through the API with the service - we have not detected any attempts to do so.

2. 18 de diciembre de 2021 a las 9:24 UTCmonitoring

   We are closely following Log4j vulnerability evolution and the latest release of Log4j 2.17.0. As we have fully removed Log4j packages from our infrastructure, we are not affected by newly found issues within Log4j packages.

3. 25 de enero de 2022 a las 15:27 UTCresolved

   This incident has been resolved. Our systems were not compromised nor affected by the Log4j vulnerability.

1. 16 de noviembre de 2021 a las 18:00 UTCinvestigating

   We are experiencing downtime on our main app and analytics due to worldwide Google Cloud downtime. We are investigating.

2. 16 de noviembre de 2021 a las 18:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 16 de noviembre de 2021 a las 18:12 UTCidentified

   Incident identified and confirmed to relate to Google Cloud platform global network issues. https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh

4. 16 de noviembre de 2021 a las 18:16 UTCmonitoring

   All systems are back to normal and we are monitoring the Google Cloud's status.

5. 16 de noviembre de 2021 a las 20:13 UTCresolved

   The issue with Google Cloud Networking has been resolved for all affected projects as of Tuesday, 2021-11-16 11:28 US/Pacific. https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh

1. 8 de noviembre de 2021 a las 9:17 UTCinvestigating

   We are experiencing degraded performance on Inline Manual Portal. This affects only users within the Inline Manual Portal at app.inlinemanual.com making some pages unavailable. The end-users consuming the player are not affected.

2. 8 de noviembre de 2021 a las 12:27 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 8 de noviembre de 2021 a las 17:26 UTCresolved

   This incident has been resolved.

1. 16 de julio de 2021 a las 9:22 UTCinvestigating

   We are currently investigating this issue.

2. 16 de julio de 2021 a las 9:30 UTCmonitoring

   We have identified the problem and fixed the primary cause. We continue monitoring the situation.

3. 16 de julio de 2021 a las 12:24 UTCresolved

   This incident has been resolved.