T09 · Insecure Skill Coding Practices
- Location
references/1-机构/接入指南/接入质量检查.md:207- Finding
Potential Disclosure of Sensitive Payment Logs and Source Code Through Email
- Content
View full analysis
- ` - The body must include: - A list of integrated products - Item-by-item check results for each module. It is recommended to attach a sample log or a screenshot of a code snippet as evidence. - Primary contact person and contact information ``` ```markdown | # | Brief check item | Passed | Sample log / code snippet | |---|------------------|--------|---------------------------| | 1 | xxx | Yes | Attach log or screenshot | | 2 | xxx | Yes | ... | Send the contents of this report by email to technical support (`WXP_GlobalTS@tencent.com`) and wait for confirmation. ``` ```markdown | Step 3: Reply to technical support by email and provide a sample log | Pending | ``` ### Technical Analysis The quality-assurance workflow directs users to transmit sample logs, source-code snippets or screenshots, merchant identifiers, and contact details through email. It does not require users to redact secrets or personal information, verify the recipient through an independently trusted channel, minimize the submitted data, or use an approved encrypted support portal. Payment integration logs and code can contain sensitive material such as: - API authorization headers and request signatures - Merchant or institution identifiers - Transaction and refund identifiers - ...[truncated 2712 chars]- Remediation
View remediation
