Inline Manual driftsforstyrrelser

1. 31. juli 2026 kl. 11.27 UTCinvestigating

   Vi er klar over den nyligt afslørede sårbarhed CVE- 2026- 66066 og behandler det alvorligt. Vores produktionssystemer er allerede blevet lappet. Vi foretager nu en grundig retsmedicinsk gennemgang af relevante logfiler for at bekræfte, om der var nogen forsøg på at udnytte sårbarheden, før patch blev anvendt. På nuværende tidspunkt har vi ikke fundet noget bevis for, at Inline Manual blev påvirket. Vi fortsætter undersøgelsen som en forholdsregel og vil dele en anden opdatering, når revisionen er færdig. [CVE- 2026- 66066] Mulige vilkårlige fil read and remote code execution in Active Storage variant processing - https: / / discubs.rubyonrails.org / t / cve- 2026- 66066- possible-arbity- file- read- and -remote-code-conduction- in- active- storage- variant- processing / 91432

2. 31. juli 2026 kl. 19.08 UTCinvestigating

   Vi fortsætter med at gennemgå vores logfiler for eventuelle tegn på, at CVE-2026-66066 blev udnyttet, før vores systemer blev lappet. Indtil videre har vi ikke fundet tegn på skadelig aktivitet i forbindelse med denne sårbarhed. Vores hurtige reaktion synes at have forhindret enhver udnyttelse, og vi har også roteret alle berørte hemmelige nøgler som en ekstra forholdsregel. Vigtigt, selv hvis en angriber havde forsøgt at udnytte denne sårbarhed, ville det ikke have givet dem adgang til kundedata. Vi har bekræftet dette baseret på, hvordan den berørte komponent er isoleret inden for vores infrastruktur. Vi vil fortsætte med at gennemgå logfiler og overvågning for enhver mistænkelig aktivitet i weekenden. Vi vil offentliggøre endnu en opdatering før, hvis vi identificerer noget relevant, eller senest mandag, 3. august, hvis der ikke er nye resultater.

3. 5. august 2026 kl. 21.13 UTCresolved

   Opløst - ingen beviser for udnyttelse Vi har afsluttet vores undersøgelse af CVE- 2026- 66066. Vi tog en bevidst grundig tilgang og gik ud over vores standard gennemgang proces for at sikre, at vi havde undersøgt alle relevante informationskilder. Dette omfattede: - Patching de berørte systemer straks - Gennemgang af ansøgninger, infrastruktur og adgangslogfiler for den pågældende periode - Søgning efter kendte indikatorer og mønstre i forbindelse med udnyttelse - Undersøgelse af usædvanlige anmodninger og aktiviteter mere detaljeret - Rotere alle potentielt berørte hemmelige nøgler som en sikkerhedsforanstaltning - Fortsat forbedret overvågning efter den indledende revision blev afsluttet - Kontrol af, at den berørte komponent ikke kunne give adgang til kundedata Efter at have afsluttet dette arbejde har vi fundet ingen beviser for, at sårbarheden blev udnyttet, eller at Inline Manual blev påvirket. Vi markerer derfor denne hændelse som løst. Vi vil fortsætte med at følge vores normale sikkerhedskontrolprocesser og vil træffe yderligere foranstaltninger, hvis nye oplysninger bliver tilgængelige. Tak. Marek og holdet

Automatisk oversat fra den officielle hændelsesopdatering.

1. 8. oktober 2024 kl. 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. oktober 2024 kl. 04.00 UTCidentified

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

3. 8. oktober 2024 kl. 04.08 UTCmonitoring

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

4. 8. oktober 2024 kl. 04.29 UTCresolved

   This incident has been resolved.

1. 30. marts 2024 kl. 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. marts 2024 kl. 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. december 2023 kl. 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. december 2023 kl. 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. december 2023 kl. 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. december 2023 kl. 17.23 UTCresolved

   This incident has been resolved.

1. 11. januar 2023 kl. 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. januar 2023 kl. 21.50 UTCidentified

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

3. 11. januar 2023 kl. 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. januar 2023 kl. 17.47 UTCresolved

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

1. 16. december 2021 kl. 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. december 2021 kl. 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. januar 2022 kl. 15.27 UTCresolved

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

1. 16. november 2021 kl. 18.00 UTCinvestigating

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

2. 16. november 2021 kl. 18.01 UTCinvestigating

   We are continuing to investigate this issue.

3. 16. november 2021 kl. 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. november 2021 kl. 18.16 UTCmonitoring

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

5. 16. november 2021 kl. 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. november 2021 kl. 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. november 2021 kl. 12.27 UTCmonitoring

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

3. 8. november 2021 kl. 17.26 UTCresolved

   This incident has been resolved.

1. 16. juli 2021 kl. 09.22 UTCinvestigating

   We are currently investigating this issue.

2. 16. juli 2021 kl. 09.30 UTCmonitoring

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

3. 16. juli 2021 kl. 12.24 UTCresolved

   This incident has been resolved.