Inline Manual 中断历史

1. 2026年7月31日 UTC 11:27investigating

   我们知道最近披露的CVE-2026-66066的脆弱性,正在认真对待它。 我们的生产系统已经修复了 我们现在正在对相关日志进行彻底的法证审查,以确定在施放补丁之前是否有利用脆弱性的任何企图。 现阶段,我们没有发现任何证据表明《内线手册》受到影响。 作为一项预防措施,我们正在继续进行调查,并将在审查完成后再提供一份最新情况。 [CVE-2026-66066] (中文(中国大陆) ). 动态存储变体处理中可能任意读取和远程代码执行 - https://discuss.rubyonrails.org/t/cve-2026-66066-possible-arbitory-file-read-和-remote-code-execution-in-active-storage-vanant-process-91432

2. 2026年7月31日 UTC 19:08investigating

   我们正在继续审查我们的日志,以查明CVE-2026-66066在系统被修补之前被利用的迹象。 迄今为止,我们没有发现与这种脆弱性有关的恶意活动的证据。 我们的快速反应似乎已经防止了任何剥削,我们还将所有受影响的密钥旋转,作为额外的预防措施。 重要的是,即使攻击者试图利用这种脆弱性,也不会让他们获得客户数据。 我们基于受影响部分如何被孤立在我们基础设施中,确认了这一点。 我们将在周末继续审查记录和监测任何可疑活动。 如果我们发现任何相关情况,我们将更早地发表另一份最新情况,或者,如果没有新的调查结果,最迟于8月3日星期一公布.

3. 2026年8月5日 UTC 21:13resolved

   已解决----无剥削证据 我们完成了对CVE-2026-66066潜在影响的调查。 我们故意采取了彻底的做法,超越了我们的标准审查进程,以确保我们审查了所有有关的信息来源。 其中包括: - 立即补补受影响的系统 - 审查所涉期间的应用、基础设施和访问记录 - 寻找与开采有关的已知指标和模式 - 更详细地调查异常请求和活动 - 旋转所有可能影响的秘密钥匙,作为预防措施 - 在初步审查完成后继续加强监测 - 核实受影响的部分无法提供客户数据 在完成这项工作后,我们发现没有证据表明脆弱性被利用,或《内线手册》受到影响。 因此,我们将这一事件定为已解决事件。 我们将继续跟踪我们正常的安全监测进程,并在获得任何新信息时采取进一步行动。 谢谢 马雷克和球队

自动翻译自官方事件更新。

1. 2024年10月8日 UTC 03:51investigating

   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. 2024年10月8日 UTC 04:00identified

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

3. 2024年10月8日 UTC 04:08monitoring

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

4. 2024年10月8日 UTC 04:29resolved

   This incident has been resolved.

1. 2024年3月30日 UTC 11:10investigating

   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. 2024年3月30日 UTC 12:28resolved

   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. 2023年12月5日 UTC 10:53investigating

   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. 2023年12月5日 UTC 10:54identified

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

3. 2023年12月5日 UTC 11:03monitoring

   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. 2023年12月5日 UTC 17:23resolved

   This incident has been resolved.

1. 2023年1月11日 UTC 20:48investigating

   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. 2023年1月11日 UTC 21:50identified

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

3. 2023年1月11日 UTC 22:04monitoring

   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. 2023年1月25日 UTC 17:47resolved

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

1. 2021年12月16日 UTC 10:35monitoring

   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. 2021年12月18日 UTC 09:24monitoring

   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. 2022年1月25日 UTC 15:27resolved

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

1. 2021年11月16日 UTC 18:00investigating

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

2. 2021年11月16日 UTC 18:01investigating

   We are continuing to investigate this issue.

3. 2021年11月16日 UTC 18:12identified

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

4. 2021年11月16日 UTC 18:16monitoring

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

5. 2021年11月16日 UTC 20:13resolved

   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. 2021年11月8日 UTC 09:17investigating

   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. 2021年11月8日 UTC 12:27monitoring

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

3. 2021年11月8日 UTC 17:26resolved

   This incident has been resolved.

1. 2021年7月16日 UTC 09:22investigating

   We are currently investigating this issue.

2. 2021年7月16日 UTC 09:30monitoring

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

3. 2021年7月16日 UTC 12:24resolved

   This incident has been resolved.