Back to feed
News Story
Geek (X)
1 sources

ZCode apologizes for security issues, open-sources code after CAICT and NSFOCUS assessments

The ZCode team completed remediation for product security issues reported by the community and issued a public apology, while open-sourcing ZCode for community scrutiny. The team stated that no code data was retained or used for model training, and invited CAICT and NSFOCUS to conduct security assessments, which confirmed the OSS bucket is in a zero-data state and that the v3.14.0 client has been remediated with the Repo Wiki feature removed.

SynthePulse Insight · AI deep readingMembers

The ZCode Security Incident: Why a "Remediation Completed" Statement Failed to Convince the Community

Version 1 · 1 source

ZCode officially stated it had completed remediation of the product security issues reported by the community, open-sourced the code, and asked CAICT and NSFOCUS to issue assessment conclusions; but on the same timeline, developers' questions about "who discovered the problem first," "open-source edition rights," and "data bucket traffic" formed a second reading of that statement.

  • ZCode officially stated: necessary remediation of the product security issues reported by the community has been completed, and it apologized to all users.
  • The official statement said ZCode has been open-sourced (github.com/zai-org/ZCode), letting the code be scrutinized by the community.
  • The official statement said CAICT and NSFOCUS were invited to conduct a security assessment: CAICT confirmed the zcode-prod Alibaba Cloud OSS bucket is in a zero-data state, and NSFOCUS confirmed all data objects and buckets have been deleted.
Open section navigationThe Core of the Statement: Remediation, Open-Sourcing, and the Assessment Conclusions of Two Institutions

The Core of the Statement: Remediation, Open-Sourcing, and the Assessment Conclusions of Two Institutions

In responding to the product security issues reported by the community, ZCode officially stated that the necessary remediation had been completed and apologized to all users. The statement also gave two actions: first, open-sourcing ZCode at github.com/zai-org/ZCode, placing the code under community scrutiny; second, inviting the China Academy of Information and Communications Technology (CAICT) and NSFOCUS to conduct a security assessment.

According to the official account, the assessment conclusions include: CAICT confirmed that the zcode-prod Alibaba Cloud OSS bucket is in a zero-data state; NSFOCUS confirmed that all data objects and buckets have been deleted. The official statement also said that no code data was retained, nor was it used for model training. These are all contents of the official statement, and this article has not obtained independent verification.

The official statement further promised to establish a continuous product security vulnerability reporting and response process, welcomed developers to continue reviewing ZCode and reporting potential issues, and said rewards would be provided based on the severity of the reported issues. This point shifts the incident from a "one-time fix" to a "long-term mechanism," but its actual implementation effect remains to be seen.

Free for now

Read the full analysis

4 more sections of analysis, plus the full takeaway

Loading

Credibility boundary

The sole source of this article is Geek's (@geekbb) post on X, which is a secondhand relay: the ZCode official statement portion is a quotation of the official account's original text and can be regarded as a first-party position from the party involved; the comment section content (RogerBen, SnowyLake, 川处安, etc.) consists of individual users' views and is unverified. The assessment conclusions of CAICT and NSFOCUS appear only in the official statement, and this article has not obtained independent published materials from the two institutions. Therefore, any statements involving assessment conclusions, data handling, and benefit rules are treated according to the source's claims and are not treated as confirmed facts.

Primary report

Geek (X)

Primary source