Vulnerability Disclosure Policy

VULNERABILITY DISCLOSURE POLICY

Last Updated: 29 10 2026

1. PURPOSE AND SCOPE

HEFEI CHANGHONG INDUSTRY CO., LTD. ("Changhong", "we", "our", or "us") is committed to ensuring the security of our products, services, and systems. This Vulnerability Disclosure Policy ("VDP") establishes a framework for receiving, assessing, and responding to vulnerability reports from security researchers, customers, and other stakeholders.

Scope: This policy covers all Changhong products, services, websites, applications, and components that we manufacture, develop, or operate, including but not limited to:

  • Smart TV products and related software/firmware
  • Home appliance products with network connectivity
  • Official websites and web applications
  • Mobile applications developed by Changhong
  • Cloud services and APIs provided by Changhong

Third-Party Components: Third-party components integrated into Changhong products are within scope when a vulnerability in such a component may affect the security of Changhong products or services. Please report such issues to us through the channels above; Changhong acts as the single point of contact and will coordinate with the relevant third-party suppliers, open-source maintainers, or other upstream stakeholders.

2. REPORTING CHANNELS

We provide multiple channels for vulnerability reporting to ensure accessibility:

  • Web Form (Preferred): Submit Vulnerabilities
  • Email: security@changhong.com (temporary placeholder, to be replaced)
  • Phone: 0551-69107519
  • PGP Key: Available upon request for encrypted communication

We accept reports in English and Chinese. We will not reject a report solely because it was submitted through another reasonable communication channel; reports received through any of the channels above are handled under this policy on an equal basis.

3. VULNERABILITY REPORT REQUIREMENTS

To help us assess and respond to your report efficiently, please include the following information:

  • Product or service affected (including version numbers)
  • Type of vulnerability (e.g., XSS, SQL Injection, RCE, Authentication Bypass)
  • Detailed description of the vulnerability
  • Step-by-step reproduction instructions
  • Proof of concept (screenshots, videos, or code)
  • Potential impact and severity assessment
  • Contact information (optional; without an email address we cannot send you progress updates)

Reports with insufficient information may delay our response. We may request additional details during the assessment process.

4. COMMUNICATION EXPECTATIONS

We are committed to maintaining timely and transparent communication throughout the vulnerability handling process:

StageTimelineCommunication
AcknowledgementWithin 7 calendar daysConfirmation with tracking number
Initial AssessmentWithin 14 calendar daysSeverity classification and validation status
RemediationBased on severity (see SLA)Progress updates every 14 days
DisclosureAfter fix availabilityCoordinated disclosure with reporter

Communication Channel: If you provide an email address, we will communicate with you at that address. For urgent matters, we may request additional contact methods. Reports submitted anonymously are still accepted and handled under this policy, but we will not be able to send individual progress updates because no contact information is available.

5. VULNERABILITY HANDLING PROCESS

Our vulnerability handling process follows industry best practices:

  1. Receipt & Acknowledgement: We receive your report and send a confirmation with a unique tracking number.
  2. Triage & Validation: Our security team assesses the report, validates the vulnerability, and classifies severity.
  3. Remediation Development: We develop and test fixes according to our SLA targets.
  4. Coordinated Disclosure: We work with you to determine appropriate disclosure timing.
  5. Publication: We publish security advisories and updates.
  6. Post-Remediation: We monitor the effectiveness of the fix and update as needed.

6. REMEDIATION SLA TARGETS

We target the following remediation timelines based on vulnerability severity:

SeverityDescriptionTarget Fix Time
CriticalRemote code execution, data breach, authentication bypass30 days
HighPrivilege escalation, significant information disclosure60 days
MediumLimited impact vulnerabilities requiring specific conditions90 days
LowMinimal impact, defense-in-depth issues180 days

These are target timelines and may vary based on complexity, third-party dependencies, and availability of patches.

7. AUTHORIZED SECURITY TESTING

We authorize security researchers to conduct non-malicious security testing on our products and services, subject to the following conditions:

  • Testing must not degrade service availability or performance
  • Testing must not access, modify, or delete user data without authorization
  • Testing must not violate applicable laws or regulations
  • Discovered vulnerabilities must be reported through our official channels
  • Vulnerability information must not be disclosed publicly without our coordination

Security testing conducted in accordance with this policy will not result in legal action by Changhong, provided the researcher acts in good faith and complies with these conditions.

8. CONFIDENTIALITY AND DISCLOSURE

Confidentiality: We treat all vulnerability reports as confidential information. Access is restricted to authorized personnel on a need-to-know basis.

Coordinated Disclosure: We prefer coordinated disclosure, where vulnerabilities are published after a fix is available. We will work with reporters to agree on disclosure timing.

Embargo Period: In some cases, we may request an embargo period to allow customers to apply patches before public disclosure. Embargo periods are negotiated case-by-case.

Third-Party Coordination: We may share relevant vulnerability information with affected component suppliers, open-source maintainers, service providers, coordinators, or other parties necessary to investigate or remediate the vulnerability. Information will be limited to what is reasonably necessary and, where appropriate, shared under confidentiality or coordinated disclosure arrangements. Where practicable, we will inform the reporter before sharing identifying information with a third party.

We will not disclose the reporter's identity to third parties without permission, unless required by applicable law.

Public Disclosure: If we are unable to reach agreement on disclosure timing, reporters may publish their findings after 90 days from the initial report, provided we have been kept informed of progress.

9. ACKNOWLEDGEMENT OF REPORTERS

We recognize and appreciate the contributions of security researchers. With your permission, we will acknowledge your contribution in our security advisories and on our Security Advisories page.

If you prefer to remain anonymous, please indicate this in your report. We will respect your wishes.

10. POLICY UPDATES

We may update this policy periodically to reflect changes in our practices, legal requirements, or industry standards. The "Last Updated" date at the top of this page indicates the most recent revision. We encourage reporters to review this policy before submitting reports.

CONTACT INFORMATION

Web Form: Submit Vulnerabilities

Email: security@changhong.com (temporary placeholder)

Phone: 0551-69107519

Security.txt: /.well-known/security.txt

Address: NO. 6069 FANGXING ROAD, ECONOMIC & TECHNOLOGICAL DEVELOPMENT ZONE, HEFEI, ANHUI, CHINA