Histórico de interrupções do Inline Manual

1. 31 Gouere 2026 da 11:27 UTCinvestigating

   Estamos cientes da vulnerabilidade recentemente divulgada CVE-2026-66066 e estamos tratando-a seriamente. Nossos sistemas de produção já foram remendados. Estamos agora a realizar uma análise forense completa dos registos relevantes para confirmar se houve alguma tentativa de explorar a vulnerabilidade antes da aplicação do sistema. Nesta fase, não encontramos nenhuma evidência de que o Manual Inline foi afetado. Continuamos a investigação como precaução e compartilharemos outra atualização assim que a revisão estiver concluída. [CVE-2026-66066] Possível leitura arbitrária de arquivos e execução de código remoto no processamento variante de armazenamento ativo - https://discuss.rubyonals.org/t/cve-2026-66066-possível-arbitrário-file-read-and-remote-code-execution-in-active-storage-variant-processing/91432

2. 31 Gouere 2026 da 19:08 UTCinvestigating

   Estamos continuando a rever nossos registros para quaisquer sinais de que CVE-2026-66066 foi explorado antes de nossos sistemas foram remendados. Até agora, não encontramos evidência de atividade maliciosa relacionada a essa vulnerabilidade. A nossa rápida resposta parece ter impedido qualquer exploração, e também rodámos todas as chaves secretas afectadas como precaução adicional. Importante, mesmo que um atacante tivesse tentado explorar essa vulnerabilidade, não teria dado a eles acesso aos dados do cliente. Confirmámos isto com base na forma como o componente afectado está isolado dentro da nossa infra-estrutura. Continuaremos a rever os registos e a monitorizar qualquer actividade suspeita durante o fim-de-semana. Publicaremos outra atualização mais cedo se identificarmos algo relevante, ou até segunda-feira, 3 de agosto, o mais tardar, se não houver novas descobertas.

3. 5 Eost 2026 da 21:13 UTCresolved

   Resolução - nenhuma evidência de exploração Concluímos nossa investigação sobre o potencial impacto da CVE-2026-66066. Tomámos uma abordagem deliberadamente exaustiva e ultrapassámos o nosso processo de revisão normal para garantir que tínhamos examinado todas as fontes de informação relevantes. Isto incluía: - Patching os sistemas afetados imediatamente - Revisão de pedidos, infra-estruturas e registos de acesso relativos ao período relevante - Pesquisa de indicadores e padrões conhecidos associados à exploração - Investigar pedidos e atividades incomuns em maior detalhe - Rotacionando todas as chaves secretas potencialmente afetadas como precaução - Continuação do acompanhamento reforçado após a revisão inicial ter sido concluída - Verificando que o componente afetado não poderia fornecer acesso aos dados do cliente Após a conclusão deste trabalho, encontramos zero evidências de que a vulnerabilidade foi explorada ou que o Manual Inline foi afetado. Estamos, portanto, a marcar este incidente como resolvido. Continuaremos a seguir os nossos processos normais de monitorização da segurança e tomaremos novas medidas se houver novas informações disponíveis. Obrigado. Marek e a equipa

Traduzido automaticamente da atualização oficial do incidente.

1. 8 Here 2024 da 03: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 Here 2024 da 04:00 UTCidentified

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

3. 8 Here 2024 da 04:08 UTCmonitoring

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

4. 8 Here 2024 da 04:29 UTCresolved

   This incident has been resolved.

1. 30 Meurzh 2024 da 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 Meurzh 2024 da 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 Kerzu 2023 da 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 Kerzu 2023 da 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 Kerzu 2023 da 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 Kerzu 2023 da 17:23 UTCresolved

   This incident has been resolved.

1. 11 Genver 2023 da 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 Genver 2023 da 21:50 UTCidentified

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

3. 11 Genver 2023 da 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 Genver 2023 da 17:47 UTCresolved

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

1. 16 Kerzu 2021 da 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 Kerzu 2021 da 09: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 Genver 2022 da 15:27 UTCresolved

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

1. 16 Du 2021 da 18:00 UTCinvestigating

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

2. 16 Du 2021 da 18:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 16 Du 2021 da 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 Du 2021 da 18:16 UTCmonitoring

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

5. 16 Du 2021 da 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 Du 2021 da 09: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 Du 2021 da 12:27 UTCmonitoring

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

3. 8 Du 2021 da 17:26 UTCresolved

   This incident has been resolved.

1. 16 Gouere 2021 da 09:22 UTCinvestigating

   We are currently investigating this issue.

2. 16 Gouere 2021 da 09:30 UTCmonitoring

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

3. 16 Gouere 2021 da 12:24 UTCresolved

   This incident has been resolved.