Istoricul incidentelor Inline Manual

1. 31 iulie 2026 la 11:27 UTCinvestigating

   Suntem conștienți de vulnerabilitatea recent dezvăluită CVE-2026-66066 și o tratează în mod serios. Sistemele noastre de producţie au fost deja patch-uri. Facem acum o analiză criminalistică completă a jurnalelor relevante pentru a confirma dacă a existat vreo încercare de a exploata vulnerabilitatea înainte de aplicarea plasturelui. În acest stadiu, nu am găsit nicio dovadă că Manualul Inline a fost afectat. Continuăm investigaţia ca măsură de precauţie şi vom împărtăşi o altă actualizare după finalizarea revizuirii. [CVE-2026-66066] Posibilă citire arbitrară a fișierelor și execuție de coduri la distanță în procesarea variantelor de stocare activă - https://discuss.rubyonrails.org/t/cve-2026-66066-possible-arbitrary-file-read-and-remote-code-execution-in-active-pove-variant-prelucration/91432

2. 31 iulie 2026 la 19:08 UTCinvestigating

   Continuăm să ne revizuim jurnalele pentru orice semn că CVE-2026-66066 a fost exploatat înainte ca sistemele noastre să fie patch-uri. Până în prezent, nu am găsit nicio dovadă de activitate maliţioasă legată de această vulnerabilitate. Răspunsul nostru rapid pare să fi împiedicat orice exploatare, și am rotit, de asemenea, toate cheile secrete afectate ca o precauție suplimentară. Important, chiar dacă un atacator ar fi încercat să exploateze această vulnerabilitate, nu le-ar fi dat acces la datele clienților. Am confirmat acest lucru pe baza modului în care componenta afectată este izolată în cadrul infrastructurii noastre. Vom continua revizuirea jurnalelor și monitorizarea pentru orice activitate suspectă în weekend. Vom publica o altă actualizare mai devreme dacă identificăm ceva relevant, sau până luni, 3 august cel târziu, dacă nu există noi constatări.

3. 5 august 2026 la 21:13 UTCresolved

   Rezolvată - nicio dovadă a exploatării Am finalizat investigaţia privind impactul potenţial al CVE-2026-66066. Am luat în mod deliberat o abordare aprofundată și am mers dincolo de procesul nostru standard de revizuire pentru a ne asigura că am examinat fiecare sursă relevantă de informații. Acestea au inclus: - Plasarea sistemelor afectate imediat - Revizuirea aplicaţiilor, infrastructurii şi jurnalelor de acces care acoperă perioada relevantă - Cautare indicatori si modele cunoscute asociate cu exploatarea - Investigarea cererilor şi activităţii neobişnuite în detaliu - Rotirea tuturor cheilor secrete potenţial afectate ca măsură de precauţie - Continuarea monitorizării consolidate după finalizarea revizuirii iniţiale - Verificarea faptului că componenta afectată nu a putut oferi acces la datele clienților După finalizarea acestei lucrări, am găsit zero dovezi că vulnerabilitatea a fost exploatată sau că Manualul Inline a fost afectat. Prin urmare, marcăm acest incident ca fiind rezolvat. Vom continua să urmărim procesele noastre normale de monitorizare a securității și vom lua măsuri suplimentare dacă vor fi disponibile noi informații. Mulţumesc. Marek şi echipa

Traducere automată din actualizarea oficială a incidentului.

1. 8 octombrie 2024 la 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 octombrie 2024 la 04:00 UTCidentified

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

3. 8 octombrie 2024 la 04:08 UTCmonitoring

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

4. 8 octombrie 2024 la 04:29 UTCresolved

   This incident has been resolved.

1. 30 martie 2024 la 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 martie 2024 la 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 decembrie 2023 la 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 decembrie 2023 la 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 decembrie 2023 la 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 decembrie 2023 la 17:23 UTCresolved

   This incident has been resolved.

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

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

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

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

1. 16 decembrie 2021 la 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 decembrie 2021 la 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 ianuarie 2022 la 15:27 UTCresolved

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

1. 16 noiembrie 2021 la 18:00 UTCinvestigating

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

2. 16 noiembrie 2021 la 18:01 UTCinvestigating

   We are continuing to investigate this issue.

3. 16 noiembrie 2021 la 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 noiembrie 2021 la 18:16 UTCmonitoring

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

5. 16 noiembrie 2021 la 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 noiembrie 2021 la 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 noiembrie 2021 la 12:27 UTCmonitoring

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

3. 8 noiembrie 2021 la 17:26 UTCresolved

   This incident has been resolved.

1. 16 iulie 2021 la 09:22 UTCinvestigating

   We are currently investigating this issue.

2. 16 iulie 2021 la 09:30 UTCmonitoring

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

3. 16 iulie 2021 la 12:24 UTCresolved

   This incident has been resolved.