T09 · Insecure Skill Coding Practices
- Location
references/03-六大系统.md:392- Finding
Overbroad disclosure and immutable storage of sensitive business records
- Content
View full analysis
Vulnerability Details
File Location:
references/03-六大系统.md:58-66references/03-六大系统.md:184-192references/03-六大系统.md:392-419references/04-财务税务.md:21-29references/04-财务税务.md:218-252references/05-信用评级.md:189-199
Vulnerability Type: Excessive data exposure and unsafe immutable storage
Risk Level: MediumVulnerable Documentation Excerpts
The following excerpts are faithful English translations of the source text:
text 1. Select a template based on the SPV type 2. Enter contribution weights, allocation ratios, and milestones 3. Compliance review 4. Electronic signature 5. Store signature information as evidence on a blockchain 6. Generate the initial contribution weightstext Account operating rules: - Authorization: authorization by two people - Large transactions: transactions of at least 50,000 require three people - Notification: notify all members of every operation by SMS or email in real time - Daily automatic reconciliation - Generate a weekly statementtext 7. Blockchain evidence storage: place all nodes on-chain Blockchain evidence storage: Place data from the entire system on-chain.text Online banking configuration: - Query permission: open to all members - Transfer permission: authorization by two peopletext Step 7: Tax payment evidence Generate tax payment evidence and make it available to all members. Each member declares individual income tax independently.text Credit disclosure: - Monthly credit score and grade: available to all members - Upgraded member list: available to all members - Downgrade reasons: visible to all members - Serious misconduct: visible to all members - Complete scoring details: visible only to the affected individualTechnical Analysis
The proposed workflow processes contracts, electronic signatures, invoices, bank records, ...[truncated 2600 chars]
- Remediation
View remediation
Remediation Suggestions
- Keep source records off-chain. Store contracts, invoices, bank records, tax evidence, signatures, and disciplinary evidence in an encrypted document repository. Put only a salted cryptographic hash, timestamp, record type, and non-sensitive identifier on-chain.
- Implement project-scoped RBAC. Separate permissions for project members, finance operators, supervisors, compliance personnel, and auditors. Membership alone must not provide access to all financial or contractual records.
- Apply field-level masking. Mask account numbers, identity numbers, telephone numbers, addresses, signatures, tax identifiers, and unrelated transaction details.
- Restrict notifications. Send transaction alerts only to authorized account custodians, finance personnel, and designated supervisors. Other members should receive sanitized aggregate reports.
- Minimize reputation disclosure. Make detailed scoring evidence available only to the affected person and authorized reviewers. Publish only the minimum status required for project eligibility.
- Define retention and correction controls. Establish retention periods, secure deletion procedures, correction workflows, appeal handling, and methods for superseding incorrect blockchain commitments.
- Require encryption and audit logging. Encrypt data in transit and at rest, use strong authentication, and record access to sensitive documents in tamper-evident audit logs.
- Perform a privacy and data-flow review. Classify every stored field and document before implementing the proposed platform or integrating electronic-signature, payment, or blockchain providers.
