关于PHP脆弱性的信息(php2shell)
Pending
- monitoring
现状:信息,无影响 我们意识到最近披露的PHP脆弱性称为“php2shell”(CVE-2026-109618和CVE-2026-109619)。 我们已评估了脆弱性,并可以确认它不影响Viedoc套房。 我们的客户无需采取任何行动,也不会影响您数据的提供、安全或完整性。 我们继续监测局势,以此作为我们标准安全进程的一部分。 如果有什么变化,我们将更新这一通知.
自动翻译自官方事件更新。
50 Viedoc incidents · 2024年3月 — official updates, affected components, duration and resolution details.
现状:信息,无影响 我们意识到最近披露的PHP脆弱性称为“php2shell”(CVE-2026-109618和CVE-2026-109619)。 我们已评估了脆弱性,并可以确认它不影响Viedoc套房。 我们的客户无需采取任何行动,也不会影响您数据的提供、安全或完整性。 我们继续监测局势,以此作为我们标准安全进程的一部分。 如果有什么变化,我们将更新这一通知.
自动翻译自官方事件更新。
Viedoc EDC行动引发的电子邮件提醒在以下时间窗口中欧盟生产实例间歇性故障: 8月31日星期一 11:02-17:25 CEST 9月3日星期四,13:31 CEST — 9月4日星期五,22:07 CEST 大多数电子邮件按预期发送,但一个子集被延迟,或在某些情况下根本没有发送。 没有其他情况受到影响。 我们正在积极调查,并将在获得更多信息后公布最新情况.
自上次报告以来,我们没有看到任何新的电子邮件故障。 我们现在正在监测局势,一旦我们确认问题已完全解决,我们将公布进一步的最新情况.
这一事件已经得到解决.
** 欧盟生产实例的Sporadic电子邮件故障** ** 说明 在下面的两个窗口中,由维多克的行动引发的电子邮件提醒被断断续续地发送. 多数已按预期交付。 一个子集被延迟,有些根本没有交付. * 8月31日星期一,11:02-17:25 * 9月3日,星期四 13:31 CEST — 9月4日,星期五 22:07 CEST Viedoc的电子邮件提醒在用户保存数据时不会被应用程序发送. 由背景处理产生 之后立即运行 根据你的研究配置决定 需要发出警报 在这两个窗口中,背景处理并不总是完成的,因此它原本会产生的警报被延迟或从未产生. 用户在这些期间输入和保存的数据按预期储存。 中断影响了由特定处理服务器而不是整个平台处理的工作,这就是为什么警报是断断续续的而不是完全停止的原因. ** 因为** Viedoc的背景处理贯穿了几个平行工作的服务器. 每个服务器都需要一个工作连接到一个共享的内部服务,维多克用它来安全地协调这项工作——例如,确保两个服务器永远不同时处理同一个主题. . 在这些窗口中,单个服务器失去了这种连接,没有重建. 一个受影响的服务器继续接受工作,但无法完成工作. 其它同时运行的服务器没有受到影响,这就是撞击断断续续的原因,也是平台整体看起来仍然健康的原因. ** 更正行动** * 确定并更换了受影响的服务器。 随后立即恢复正常处理,包括警报生成。 * 我们确认,随后的处理完成得正确,没有再发生电子邮件故障。 ** 预防性行动** 加强监测 我们加强了监测并增加了警报,以更快地发现任何单个服务器上的这种具体故障,防止这种故障无声地出故障。 根本原因-正在进行的调查 关于这些联系为何失败的调查仍未结束.
自动翻译自官方事件更新。
导致顾客无法在23:00至0:00之间接触. 问题是我们的基础设施,我们为不方便而道歉。 系统恢复正常,不存在保密或完整性问题。 这个问题只影响到进入我们的系统.
自动翻译自官方事件更新。
我们正经历着来自法国中部地区阿祖尔的一个平台部分的不便,这造成了一些交通损失,你可以体验到这种服务在短时间内无法提供。 我们正在调查,会随时通知你.
我们正在继续监测任何其他问题.
微软已经解决了事件 我们可以确认维多克套房再次全面运行 我们为不方便而道歉.
□ 总结 我们从法国中部地区的Azure \(Azure App Services\)的一个基本平台构件中体验到问题, 我们的系统监测立即发现问题,并通知了1分钟内作出反应的平台小组。 我们可以在15分钟之内确认,问题在于平台供应商。 □ 受影响的实例 欧洲所有产品 □ 持续时间 2026-08-17 09:32 UTC至2026-08-17 11:20 UTC开始. □ 根源 Microsoft Azure Cloud的一个基础设施部分负责在法国中部地区的Azure App Service平台内处理收到的请求,超过了业务门槛,减少了支持客户工作负荷的服务资源。 因此,维多克经历了间歇性可用性问题和失败的请求. □ 影响 这影响了维多克的可用性,同时又不影响数据自信、完整性或隐私。 □动作 跟踪平台供应商的能力.
自动翻译自官方事件更新。
我们目前正在调查这一问题,不久将进行更新.
这个问题与中国数据中心的退役有关,我们正在继续调查.
此事被确定为"阿苏克云中国"内的一个问题,我们现在已经确认这个问题已经缓解了. 一旦我们得到一个根源分析, 我们将更新一个事件报告。 我们为任何不便而道歉.
□ 总结 我们的中国地区由于我们的平台供应商在系统组件之间的内部信息传递方面存在一个配置故障而出现故障,这实际上使我们的产品套件在4小时40分钟内无法使用。 由于中国的夜间客流量通常很低,因此预计对客户的影响较低。 我们的系统监测立即发现问题,并通知我们的平台小组,该小组在1分钟之内作出答复,我们可以在1小时之内确认问题在于平台提供者。 A型支持票被登录到我们的平台提供商,他们可以确认他们确实在2小时32分钟后有问题,之后38分钟就解决了. □ 受影响的实例 中国的所有产品 □ 持续时间 2026-07-29 12:07 UTC至2026-07-29 16:47 UTC时. □ 根源 我们中国的平台提供者21ViaNet/微软Azure China的配置出错. □ 影响 仅限可用。 数据完整性和数据保密性未受影响。 □动作 与平台提供者就改进其操作程序、监测和事件应对采取后续行动.
自动翻译自官方事件更新。
自4.95释放以来,维多克 数据库中已使用协调世界时时间而不是网站的当地时区记录了我的提交材料。 如果提交时协调世界时的日期和站点的本地日期不同,维多克诊所的事件日期将错误地反映协调世界时的日期而不是本地的日期. 根据研究设计中定义的数据输入窗口,这也可能导致出窗查询. Viedoc Clinic UI中的审计线索,通过"显示历史"访问,根据当地时区显示正确的日期和时间戳. 这个问题既影响到Viedoc Me应用程序的现有版本,也影响到遗留版本。 这一问题已经确定,目前正在拟订解决办法。 固定会确保使用站点的本地时区存储新的提交文件,但不会纠正已经发生的时间戳或出窗查询. 这些问题将在今后的更新中加以解决.
我们正在积极努力以尽快解决这一问题。 目前正在最后确定并测试一个热补剂,我们估计,它将在下个星期上半个半月投入生产.
我们今天将开始向生产环境释放热量。 一旦所有实例的发行完成,将公布最新版本.
该事件已经得到解决,向所有培训和生产活动发放了热补丁4.95.2。 这一释放使问题无法反复出现。 然而,在协调世界时已经记录的事件日期目前将保持不变,这一问题已经引发的任何窗外查询也将保留到纠正为止。 目前存放在协调世界时的提交材料将在晚些时候更正。 这一更正的时间尚未确定.
自动翻译自官方事件更新。
After the Viedoc 4.95 release, when a revision is applied to a form containing a repeating item group, and a user upgrades the form from the landing page, data previously entered in the repeating item group is cleared. The issue is occurring on the EU and US training and production instances. Investigation is ongoing. Until further information is known, we advise all customers to refrain from applying revisions requiring form upgrades on forms containing repeating item groups.
The issue has been identified and a fix is being implemented.
Hotfix 4.95.1 has been released on the US training and production instances. The incident is resolved on those instances. The hotfix will be deployed to EU training and production instances tomorrow.
Hotfix 4.95.1 has been released on the EU training and production instances. The incident is now resolved on all instances.
Temporary operational disturbance observed in the Viedoc suite on the Chinese instance (clinic.viedoc.cn).
This incident has been resolved.
Operational disturbance observed in Viedoc suite on the Chinese instance (clinic.viedoc.cn). Investigations are ongoing since 05:20 CMT
The incident has been resolved since 06:40 CMT
Operational disturbance observed in Training on the Chinese instance (clinic.viedoc.cn). Investigations are ongoing.
We are continuing to investigate this issue.
This incident has been resolved.
After the Viedoc 4.94 release, the following issues affect the EU and US training and production instances: - Users cannot approve randomization configurations in Viedoc Admin when kit allocation is not used. Randomization and kit allocation in Viedoc Clinic are not affected. - WHO Drug dictionary terms are not loading as expected in the legacy medical coding tool. The new medical coding tool is not affected. We are working on a fix for these issues.
After the Viedoc 4.94 release, the following issues affect the EU and US training and production instances: - Users cannot approve randomization configurations in Viedoc Admin when kit allocation is not used. Randomization and kit allocation in Viedoc Clinic are not affected. - WHO Drug dictionary terms are not loading as expected in the legacy medical coding tool. The new medical coding tool is not affected. - Intermittent failures in Designer, where users are unexpectedly logged out, are affecting certain users. We are working on a fix for these issues, and the Designer issue is currently under investigation.
A hotfix is currently being prepared and will be deployed to both our EU and US instances. Based on preliminary timelines, we expect this release to go out on Monday, May 11.
This incident was resolved this morning with the release of hotfix version 4.94.1 on both the EU and US instances.
Operational disturbance observed in Viedoc 4 on the European instance (v4.viedoc.net). Investigations are ongoing.
Microsoft Azure experienced a power event at their France Central datacenter, caused by a loss of utility power from an external provider. Power has since been restored via backup generators and recovery is underway. As of now, there are no active disruptions to Viedoc services, and we continue to monitor the situation closely.
Microsoft Azure experienced a power event at their France Central datacenter, caused by a loss of utility power from an external provider. Power has since been restored via backup generators and recovery is underway. As of now, there are no active disruptions to Viedoc services, and we continue to monitor the situation closely.
This incident has been resolved.
We have received reports of intermittent delivery failures affecting text messages sent to numbers with country codes +31 (Netherlands), +32 (Belgium), +33 (France), and +44 (United Kingdom). An investigation is currently underway together with the subproccessor. The default SMS sender is changed from a phone number to "Viedoc" to reduce the risk of texts being treated as spam.
Since 10.30 CET today text messages are delivered as expected to numbers with country codes previously listed.
The User Administration Log (Excel) and Log of Users and Roles (PDF) cannot currently be generated for studies containing more than 100 users. This issue was introduced in the 4.90 release and affects all instances where version 4.90 has been deployed. The root cause has been identified, and a corrective fix is currently in preparation.
A fix has been developed and is currently undergoing testing. The fix is planned to be deployed as a hotfix.
This issue has been resolved with the release of Viedoc 4.90.1, which was deployed to all production instances on 2025-12-16. The User Administration Log (Excel) and Log of Users and Roles (PDF) can now be generated as expected, including for studies containing more than 100 users.
Since around 12.30 CET, 1st of December, Viedoc is not sending any emails from the EU and US training and production instances due to a service disruption. The issue has been identified and we are working with our subprocessor to resolve the issue. All emails triggered during the affected period have been queued and will be delivered. The incident is caused by a malfunction at one of our subprocessors.
The email queue is currently being processed, and messages are being delivered, although with a temporary delay.
The queue had been fully processed at around 9.20 PM CET on 2025-12-01. Since that time emails have been delivered without delay.
Between 13:22 CET and 14:12 CET on 25 November 2025, Viedoc did not send any emails from the EU training and production instance due to a service disruption. The issue was identified and fully resolved at 14:12 CET, after which email processing resumed as normal. All emails triggered during the affected period have been queued and will be delivered. The incident was caused by a malfunction at one of our subprocessors.
The email queue is currently being processed, and messages are being delivered, although with a temporary delay.
The queue had been fully processed at around 5.30 PM CET on 2025-11-25.
Operational disturbance observed on the Chinese instance (clinic.viedoc.cn). Resolved
The planned release of version 4.89 to the CN training and production instances has been cancelled due to unforeseen technical issues specific to the Chinese server environment. As the 4.90 release is already scheduled for December, we will proceed directly from version 4.88 to 4.90 for the CN training and production instances. The impact to end users is minimal, as version 4.89 contains only non-critical bug fixes. No other instances or regions are affected by this change. We appreciate your understanding and apologize for any inconvenience this may cause.
From approximately 23.44 UTC to 23.54 UTC, users faced issues logging in to the European production instance. Investigations to find the root cause are ongoing. No other instances were affected.
Description From approximately 23.44 UTC to 23.54 UTC on 2025-11-02, users were unable to log in to the European production instance. It is possible that users faced sporadic issues logging in also between approximately 23.00 UTC and 23.44 UTC. No other instances were affected. Cause The cause of the issue was an unexpected error in the identity provider \(idp\), leading to an accumulating memory consumption during the evening \(UTC\) of 2025-11-02. From approximately 23.00 UTC users would face sporadic failures when trying to log in. From approximately 23.44 UTC users could not log in. At 23.54 UTC on 2025-11-02 the idp was restarted, and users could log in as expected again. Corrective Action Alerts were triggered when the idp did not respond and the idp was restarted again at 2354 UTC on 2025-11-02. After the restart users could log in as expected again. Preventive Action Preliminary investigation identified a few improvements that could be made to make the idp more resilient. Implementation of these improvements have been initiated while the investigation of the issue continues.
Emails triggered from EDC actions in Viedoc has been failing sporadically on the EU production instance since approximately 9AM CEST 2025-09-02. No other instances are affected. Investigations are ongoing.
The issue has been identified and a fix is being implemented.
A fix has been implemented and emails are now being sent as expected. We will continue to monitor the situation.
Since approximately noon CEST, emails triggered from the EDC has been delivered as expected.
**Description** Between 9AM CEST on 2025-09-02 and noon CEST 2025-09-03 there were sporadic failures in email alerts expected to be triggered from Viedoc on the EU production instance. No other instances were affected. Customers were initially informed through the status page at 15.56 CEST on 2025-09-03. **Cause** On Tuesday at 9AM CEST on 2025-09-02, there was a very high load on the system. The high load on the system caused worker function apps, used to handle various processes in the EDC, to scale out to the maximum use of 20 instances in parallel. This caused failures, and in combination with in-built retry policy of failing actions, there was an overload on the system. While form save and form view continued to work as expected throughout the duration of the issue, there were sporadic errors in specific system actions in the post-processing step. * EDC email alerts, configured in the CRF design, were sporadically not sent during this time window. It did not affect all emails. * Terms defined to be coded in the medical coding tool sporadically failed to sync to Viedoc Coder. It did not affect all terms. **Corrective action** Once the root cause of the exceptions was identified, the worker function app was gradually scaled down to run on 4 instances to avoid having too many actions ongoing at the same time. This work begun around 11AM CET on 2025-09-03 and an immediate improvement could be seen. Around noon 2025-09-03 the situation was completely resolved, and all emails could be sent as expected again. Email alerts not sent during this issue could not be re-sent and will also not show up in the communication log. All terms that had not synced properly with Viedoc Coder during the issue, were synced with Viedoc Coder on the afternoon of 2025-09-03 and 2025-09-04. **Preventive action** Scaling down the worker function app to run on 4 instances is not considered to bring any noticeable impact on performance, but will ensure the same overload issue will not occur again. An evaluation will be performed if it is necessary to scale up the worker function app again and if so, how this could be done without causing any similar issues.