- Top reward
- €5,000
- Top severity paid
- Critical
- Assets in scope
- 2
- Public CVEs
- 46
- Last change
At a glance
What to know before you start testing.
- Pays up to €5,000
- for critical bugs, from €8.
- Report through their form
- en.security.tencent.com/index.php/report/add
- No public write-ups
- Keep findings private.
Rewards
What YesWeHack lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
€6,425 |
| High |
|
€780 |
| Medium |
|
€130 |
| Low |
|
€32 |
- Hall of fame
-
Yes
Any qualifying report that results in a change being made will at a minimum receive the Hall of Fame recognition.
Summarised with AI from the program policy on YesWeHack, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
2 assets you may test, 6 excluded.
Products and areas 2
- Core Assets In-Scope Products (for the full list please visit https://en.security.tencent.com/index.php/policy)
- Non Core Assets In-Scope Products (for the full list please visit https://en.security.tencent.com/index.php/policy)
Out of scope (6)
- *Notes about Tencent Cloud (cloud.tencent.com as included in *.tencent.com)
- Only vulnerabilities affecting the platform itself and IP owned by Tencent will be accepted. If an IP belongs to Tencent Cloud external customer, it is not considered in scope.
- Please note that the vulnerabilities reported for the following assets will not be eligible for bounties.
- Third-party applications and websites
- *. myqcloud.com
- *.qzoneapp.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Tencent Bug Bounty Program (via YesWeHack)'s policy. "We" in these lines means the program, not this site.
While testing
-
You must be above the age of 18 (or the relevant age in your jurisdiction where you are considered a minor)
-
You must be the first reporter of the vulnerability
-
Your report must be your own work, and you have not used information owned by another person or entity.
-
Please provide detailed reports with reproducible steps.
-
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
-
When testing, you must only use and only interact with your own test accounts in order to respect our users' privacy
-
You will not interact with another user's account without that user's prior written consent
-
It is strictly forbidden to publicly disclose the vulnerability prior to the report being closed by us, the vulnerability being fixed and you receiving a written authorization from us.
Not accepted
-
"Self" XSS
-
Session fixation
-
Content Spoofing
-
Missing cookie flags
-
SSL/TLS best practices
-
Mixed content warnings
-
Clickjacking/UI redressing
-
Flash-based vulnerabilities
-
Admin panel can be brute force
-
Local denial of service of Mobile APP
-
Reflected file download attacks (RFD)
-
Physical or social engineering attacks
-
Feedback,comment,message,etc. flooding
-
SMS/Email flooding for some of our business
-
CSRF/XSS with long or unpredictable parameter
-
Login/logout/unauthenticated/low-impact CSRF
-
Unverified Results of automated tools or scanners
-
No SPF/DMARC in non-email domains/subdomains
-
Attacks requiring MITM or physical access to a user's device
-
Issues related to networking protocols or industry standards
-
Error information disclosure that cannot be used to make a direct attack
-
Missing security-related HTTP headers which do not lead directly to a vulnerability
-
Information leakage that cannot be used to make a direct attack,like server IP,server version,path,error message,internal IP,etc.
Summarised with AI from the program policy on YesWeHack, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope removed
In-Scope Products (for the full list please visit https://en.security.tencent.com/index.php/policy)
-
Scope added
Non Core Assets In-Scope Products (for the full list please visit https://en.security.tencent.com/index.php/policy)
-
Scope added
Core Assets In-Scope Products (for the full list please visit https://en.security.tencent.com/index.php/policy)
-
Scope added
Only vulnerabilities affecting the platform itself and IP owned by Tencent will be accepted. If an IP belongs to Tencent Cloud external cust... (out of scope)
-
Scope added
*Notes about Tencent Cloud (cloud.tencent.com as included in *.tencent.com) (out of scope)
-
Scope added
Third-party applications and websites (out of scope)
-
Scope added
*. myqcloud.com (out of scope)
-
Scope added
*.qzoneapp.com (out of scope)
-
Scope added
Please note that the vulnerabilities reported for the following assets will not be eligible for bounties. (out of scope)
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2026-8786 | A vulnerability has been found in Tencent WeKnora up to 0.3.6. Affected by this issue is the function getKnowledgeBaseForInitialization of the file internal/handler/initialization.go of the component Config API Endpoint. The manipulation of the argument kbId leads to authorization bypass. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. | Low 2.1 | 18 May 2026 |
| CVE-2026-5585 | A vulnerability was found in Tencent AI-Infra-Guard 4.0. The affected element is an unknown function of the file common/websocket/task_manager.go of the component Task Detail Endpoint. Performing a manipulation results in information disclosure. The attack may be initiated remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not | Medium 5.5 | 5 Apr 2026 |
| CVE-2026-30858 | WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.3.0, a DNS rebinding vulnerability in the web_fetch tool allows an unauthenticated attacker to bypass URL validation and access internal resources on the server, including private IP addresses (e.g., 127.0.0.1, 192.168.x.x). By crafting a malicious domain that resolves to a publi | Medium 6.5 | 7 Mar 2026 |
| CVE-2026-30859 | WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.2.12, a broken access control vulnerability in the database query tool allows any authenticated tenant to read sensitive data belonging to other tenants, including API keys, model configurations, and private messages. The application fails to enforce tenant isolation on critical | Medium 5.3 | 7 Mar 2026 |
| CVE-2026-30860 | WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.2.12, a remote code execution (RCE) vulnerability exists in the application's database query functionality. The validation system fails to recursively inspect child nodes within PostgreSQL array expressions and row expressions, allowing attackers to bypass SQL injection protectio | Critical 9.9 | 7 Mar 2026 |
| CVE-2026-30861 | WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. From version 0.2.5 to before version 0.2.10, an unauthenticated remote code execution (RCE) vulnerability exists in the MCP stdio configuration validation. The application allows unrestricted user registration, meaning any attacker can create an account and exploit the command injection flaw. Despi | Critical 9.9 | 7 Mar 2026 |
| CVE-2026-30855 | WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.3.2, an authorization bypass in tenant management endpoints of WeKnora application allows any authenticated user to read, modify, or delete any tenant by ID. Since account registration is open to the public, this vulnerability allows any unauthenticated attacker to register an ac | High 8.8 | 7 Mar 2026 |
| CVE-2026-30856 | WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.3.0, a vulnerability involving tool name collision and indirect prompt injection allows a malicious remote MCP server to hijack tool execution. By exploiting an ambiguous naming convention in the MCP client (mcp_{service}_{tool}), an attacker can register a malicious tool that ov | Medium 5.9 | 7 Mar 2026 |
| CVE-2026-30857 | WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.3.0, a cross-tenant authorization bypass in the knowledge base copy endpoint allows any authenticated user to clone (duplicate) another tenant’s knowledge base into their own tenant by knowing/guessing the source knowledge base ID. This enables bulk data exfiltration (document/FA | Medium 5.3 | 7 Mar 2026 |
| CVE-2026-30247 | WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.2.12, the application's "Import document via URL" feature is vulnerable to Server-Side Request Forgery (SSRF) through HTTP redirects. While the backend implements comprehensive URL validation (blocking private IPs, loopback addresses, reserved hostnames, and cloud metadata endpoi | Medium 5.9 | 7 Mar 2026 |
| CVE-2025-63945 | A privilege escalation (PE) vulnerability in the Tencent iOA app thru 210.9.28693.621001 on Windows devices enables a local user to execute programs with elevated privileges. However, execution requires that the local user is able to successfully exploit a race condition. | High 7.4 | 23 Feb 2026 |
| CVE-2025-63946 | A privilege escalation (PE) vulnerability in the Tencent PC Manager app thru 17.10.28554.205 on Windows devices enables a local user to execute programs with elevated privileges. However, execution requires that the local user is able to successfully exploit a race condition. | High 7.4 | 23 Feb 2026 |
| CVE-2026-22687 | WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.2.5, after WeKnora enables the Agent service, it allows users to call the database query tool. Due to insufficient backend validation, an attacker can use prompt‑based bypass techniques to evade query restrictions and obtain sensitive information from the target server and databa | Medium 5.6 | 10 Jan 2026 |
| CVE-2026-22688 | WeKnora is an LLM-powered framework designed for deep document understanding and semantic retrieval. Prior to version 0.2.5, there is a command injection vulnerability that allows authenticated users to inject stdio_config.command/args into MCP stdio settings, causing the server to execute subprocesses using these injected values. This issue has been patched in version 0.2.5. | Critical 9.9 | 10 Jan 2026 |
| CVE-2025-13709 | Tencent TFace restore_checkpoint Deserialization of Untrusted Data Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Tencent TFace. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the restore_checkpo | High 7.8 | 23 Dec 2025 |
| CVE-2025-13711 | Tencent TFace eval Deserialization of Untrusted Data Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Tencent TFace. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the eval endpoint. The issue resu | High 7.8 | 23 Dec 2025 |
| CVE-2025-56230 | Tencent Docs Desktop 3.9.20 and earlier suffers from Missing SSL Certificate Validation in the update component. | High 7.5 | 4 Nov 2025 |
| CVE-2025-11046 | A security flaw has been discovered in Tencent WeKnora 0.1.0. This impacts the function testEmbeddingModel of the file /api/v1/initialization/embedding/test. The manipulation of the argument baseUrl results in server-side request forgery. The attack can be launched remotely. The exploit has been released to the public and may be exploited. It is advisable to upgrade the affected component. The ven | Medium 5.5 | 26 Sep 2025 |
| CVE-2024-40433 | Insecure Permissions vulnerability in Tencent wechat v.8.0.37 allows an attacker to escalate privileges via the web-view component. | High 8.8 | 26 Jul 2024 |
| CVE-2024-34408 | Tencent libpag through 4.3.51 has an integer overflow in DecodeStream::checkEndOfFile() in codec/utils/DecodeStream.cpp via a crafted PAG (Portable Animated Graphics) file. | Medium 5.3 | 3 May 2024 |
| CVE-2024-33078 | Tencent Libpag v4.3 is vulnerable to Buffer Overflow. A user can send a crafted image to trigger a overflow leading to remote code execution. | Critical 9.8 | 1 May 2024 |
| CVE-2024-22873 | Tencent Blueking CMDB v3.2.x to v3.9.x was discovered to contain a Server-Side Request Forgery (SSRF) via the event subscription function (/service/subscription.go). This vulnerability allows attackers to access internal requests via a crafted POST request. | High 8.1 | 26 Feb 2024 |
| CVE-2023-52286 | Tencent tdsqlpcloud through 1.8.5 allows unauthenticated remote attackers to discover database credentials via an index.php/api/install/get_db_info request, a related issue to CVE-2023-42387. | High 7.5 | 31 Dec 2023 |
| CVE-2023-40829 | There is an interface unauthorized access vulnerability in the background of Tencent Enterprise Wechat Privatization 2.5.x and 2.6.930000. | High 7.5 | 12 Oct 2023 |
| CVE-2023-39988 | Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in 标准云(std.Cloud) WxSync plugin <= 2.7.23 versions. | Medium 6.5 | 4 Sep 2023 |
| CVE-2023-34312 | In Tencent QQ through 9.7.8.29039 and TIM through 3.4.7.22084, QQProtect.exe and QQProtectEngine.dll do not validate pointers from inter-process communication, which leads to a write-what-where condition. | High 7.8 | 1 Jun 2023 |
| CVE-2023-30363 | vConsole v3.15.0 was discovered to contain a prototype pollution due to incorrect key and value resolution in setOptions in core.ts. | Critical 9.8 | 26 Apr 2023 |
| CVE-2022-35158 | A vulnerability in the lua parser of TscanCode tsclua v2.15.01 allows attackers to cause a Denial of Service (DoS) via a crafted lua script. | High 7.5 | 3 Aug 2022 |
| CVE-2021-33057 | The QQ application 8.7.1 for Android and iOS does not enforce the permission requirements (e.g., android.permission.ACCESS_FINE_LOCATION) for determining the device's physical location. An attacker can use qq.createMapContext to create a MapContext object, use MapContext.moveToLocation to move the center of the map to the device's location, and use MapContext.getCenterLocation to get the latitude | High 7.5 | 26 Jul 2022 |
| CVE-2021-40180 | In the WeChat application 8.0.10 for Android and iOS, a mini program can obtain sensitive information from a user's address book via wx.searchContacts. | High 7.5 | 26 Jul 2022 |
| CVE-2021-27439 | TencentOS-tiny version 3.1.0 is vulnerable to integer wrap-around in function 'tos_mmheap_alloc incorrect calculation of effective memory allocation size. This improper memory assignment can lead to arbitrary memory allocation, resulting in unexpected behavior such as a crash or a remote code injection/execution. | High 7.3 | 3 May 2022 |
| CVE-2021-33879 | Tencent GameLoop before 4.1.21.90 downloaded updates over an insecure HTTP connection. A malicious attacker in an MITM position could spoof the contents of an XML document describing an update package, replacing a download URL with one pointing to an arbitrary Windows executable. Because the only integrity check would be a comparison of the downloaded file's MD5 checksum to the one contained withi | High 8.1 | 6 Jun 2021 |
| CVE-2021-27247 | This vulnerability allows remote attackers to disclose sensitive information on affected installations of Tencent WeChat 2.9.5 desktop version. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the WXAM decoder. The issue results from the lack of proper validation of user-supplied data | Medium 6.5 | 14 Apr 2021 |
| CVE-2020-27874 | This vulnerability allows remote attackers to execute arbitrary code on affected installations of Tencent WeChat 7.0.18. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the WXAM Decoder. The issue results from the lack of proper validation of user-supplied data, which can result in a | High 8.8 | 10 Feb 2021 |
| CVE-2020-24160 | Shenzhen Tencent TIM Windows client 3.0.0.21315 has a DLL hijacking vulnerability, which can be exploited by attackers to execute malicious code. | High 7.8 | 3 Sep 2020 |
| CVE-2020-24162 | The Shenzhen Tencent app 5.8.2.5300 for PC platforms (from Tencent App Center) has a DLL hijacking vulnerability. Attackers can use this vulnerability to execute malicious code. | High 7.8 | 3 Sep 2020 |
| CVE-2020-10551 | QQBrowser before 10.5.3870.400 installs a Windows service TsService.exe. This file is writable by anyone belonging to the NT AUTHORITY\Authenticated Users group, which includes all local and remote users. This can be abused by local attackers to escalate privileges to NT AUTHORITY\SYSTEM by writing a malicious executable to the location of TsService. | High 7.8 | 9 Apr 2020 |
| CVE-2019-17151 | This vulnerability allows remote attackers redirect users to an external resource on affected installations of Tencent WeChat Prior to 7.0.9. User interaction is required to exploit this vulnerability in that the target must be within a chat session together with the attacker. The specific flaw exists within the parsing of a users profile. The issue lies in the failure to properly validate a users | Medium 5.4 | 7 Jan 2020 |
| CVE-2019-13125 | HaboMalHunter through 2.0.0.3 in Tencent Habo allows attackers to evade dynamic malware analysis via PIE compilation. | High 7.8 | 1 Jul 2019 |
| CVE-2019-11419 | vcodec2_hls_filter in libvoipCodec_v7a.so in the WeChat application through 7.0.3 for Android allows attackers to cause a denial of service (application crash) by replacing an emoji file (under the /sdcard/tencent/MicroMsg directory) with a crafted .wxgf file. The content of the replacement must be derived from the phone's IMEI. The crash occurs upon receiving a message that contains the replaced | Medium 5.5 | 14 May 2019 |
| CVE-2018-11616 | This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Tencent Foxmail 7.2.9.115. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the processing of URI handlers. The issue results from the lack of proper validation of a user-supplied strin | High 8.8 | 30 Aug 2018 |
| CVE-2018-13439 | WXPayUtil in WeChat Pay Java SDK allows XXE attacks involving a merchant notification URL. | High 7.5 | 8 Jul 2018 |
| CVE-2011-4863 | The Tencent QQPimSecure (com.tencent.qqpimsecure) application 3.0.2 for Android does not properly protect data, which allows remote attackers to read or modify SMS/MMS messages and a contact list via a crafted application. | Medium 5.8 | 25 Jan 2012 |
| CVE-2011-4864 | The Tencent MobileQQ (com.tencent.mobileqq) application 2.2 for Android does not properly protect data, which allows remote attackers to read or modify messages and a friends list via a crafted application. | Medium 5.8 | 25 Jan 2012 |
| CVE-2011-4865 | The Tencent WBlog (com.tencent.WBlog) 3.3.1 and MicroBlogPad 1.4.0 applications for Android do not properly protect data, which allows remote attackers to read or modify message drafts and search keywords via a crafted application. | Medium 5.8 | 25 Jan 2012 |
| CVE-2011-4867 | The Tencent QQPhoto (com.tencent.qqphoto) application 0.97 for Android does not properly protect data, which allows remote attackers to read or modify contact information and a password hash via a crafted application. | Medium 5.8 | 25 Jan 2012 |
Original policy
Copied from yeswehack.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Rules
Bounty Policy
Tencent looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe. If you believe you have discovered a vulnerability, kindly disclose to us responsibly via the Tencent Security Response Centre (TSRC).
This Bounty Policy governs your participation in the bounty program and forms part of the Tencent Security Response Center Terms of Service.
Note: For a smooth payment, make sure to use the same email address on both TSRC and YesWeHack. Eligible reports will be imported to the program and hunters will be able to claim them. Once claimed, these reports will be eligible for a payment.
Contact us
For any questions or clarifications, you may contact the Tencent Security Team at [email protected].
Other links:
- Tencent Security Response Centre
- WeChat Account ID: tsrc_team
Rules of Engagement
The classification of a vulnerability (Critical, High, Moderate or Low as described below), whether a product or application is in scope of the bounty program and its classification (core, important, and other in-scope), and whether to grant a monetary reward and its amount will be within the sole discretion of the Tencent Security Team, based on a number of factors including, without limitation, quality of the report, severity of the vulnerability, reproducibility of the vulnerability, its impact on our users and other products and services, ease of exploitation and many other factors.
Any design or implementation issue regarding any qualifying product that is reproducible and substantially affects the security of Tencent users is likely to be in scope for the program.
However, reports and researchers must meet the following requirements to be eligible to receive a monetary reward through YesWeHack platform:
- You must be above the age of 18 (or the relevant age in your jurisdiction where you are considered a minor)
- You must be KYC verified
- You must be the first reporter of the vulnerability (whether you are the first reporter is determined by us in our discretion and we are not obligated to share with you details related to prior reports).
- Your report must be your own work, and you have not used information owned by another person or entity.
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
- The vulnerability must demonstrate security impact to a site or application in scope (see Scope below)
- Accessing private information of other users, performing actions that may negatively affect Tencent users (e.g., spam, denial of service), or sending reports from automated tools without verifying them will immediately disqualify the report, and may result in additional steps being taken. You must comply with applicable laws and regulations, including applicable privacy laws, with respect to your disclosure and access of data.
- When testing, you must only use and only interact with your own test accounts in order to respect our users' privacy, especially those which may compromise the privacy of others. You will not interact with another user's account without that user's prior written consent (which you will make available to us upon our request).
- Vulnerability Disclosure:
- It is strictly forbidden to publicly disclose the vulnerability prior to the report being closed by us, the vulnerability being fixed and you receiving a written authorization from us.
- The disclosure and the content of the disclosure should be under the authorization of TSRC. Please take note that any form of vulnerability disclosure prior to consent from Tencent may result in disqualification from the Bounty program.
- Feel free to contact us if you have any questions.
- We are prohibited from rewarding you (such as when you are subject to trade sanctions, embargoes or denied person status).We are unable to issue rewards to individuals employed by Tencent or its subsidiaries.
Grant of License
You grant Tencent a non-exclusive, royalty-free, irrevocable, perpetual, transferable, worldwide license (with the right to sublicense) to copy, reproduce, use, modify, test, create derivative works (including commercial products) based upon, distribute, publish, display and otherwise exploit your reports and other information you provide to us under this Agreement.
Rewards
{YWH-P12821}
Rewards are stated in USD.
Severity Rating
[Critical]
{YWH-P12824}
[High]
{YWH-P12827}
[Moderate]
{YWH-P12830}
[Low]
{YWH-P12833}
All reports will be reviewed based on the impact and severity of the reported vulnerability. Any qualifying report that results in a change being made will at a minimum receive the Hall of Fame recognition.
The main categories of vulnerabilities that we are primarily concerned about are:
- Cross-site Scripting (XSS)
- Cross-site Request Forgery (CSRF)
- Server-Side Request Forgery (SSRF)
- SQL Injection
- Remote Code Execution (RCE)
- XML External Entity Attacks (XXE)
- Access Control Issues (Insecure Direct Object Reference issues, etc.)
- Exposed Administrative Panels that without strong protection
- Directory Traversal Issues
- Local File Disclosure (LFD)
- Vast Users' Sensitive Information Leakage
- Vast Order details Leakage
In-Scope Assets
Products, services and applications distributed and made available in any form by or on behalf of Tencent and described in "Core Products" and "Other In-Scope Products" below are in scope. For more information about our products and services, please visit https://www.tencent.com/en-us/business.html.
1. Core Assets
- Tencent Yuanbao (Android, iOS, Web)
- Tencent Yuanqi (Android, iOS, WinPC, Mac)
- WeChat (Android, iOS, WinPC, Mac)
- WeChat instant messaging function
- WeChat login/ticket
- WeChat address book
- WeChat Moments
- WeChat Official Account
- WeChat Mini Program main framework API
- WeCom (Android, iOS, WinPC, Mac)
- Tencent Exmail main domain (
*.exmail.qq.com) - WeCom management background
- WeCom address book
- WeCom instant messaging function
- QQ mail main domain (
*.mail.qq.com) - WeCom basic core functions (WeCom instant messaging function, enterprise payment, session content archive, Weiyun, document, fusion meeting, WeCom Moments)
- WeCom Sensitive information, such as enterprise address book list, login/ticket
- WeChat Pay function (excluding services recommended on the payment guide page grid)
- WeChat wallet
- WeChat Pay independently-developed face recognition device
- WeChat Pay independently-developed palm recognition device
- WeChat Pay merchant platform (including domestic and overseas)
- WeChat Credit card repayment
- Tenpay
- LiCaiTong
- Tencent mobile top-up
- Tencent Portfolio (腾讯自选股)
- King of Glory mobile game
- Game for Peace mobile game
- Tencent Games Joy Club
- jiazhang.qq.com (成长守护平台)
- QQ client (Android, iOS, WinPC, Mac)
- QQ basic core functions (such as instant messaging function, user profile, login/ticket, etc.)
- QQ wallet (excluding services recommended on the wallet guide page grid)
- Doc.qq.com (excluding third-party provided plugins)
- Tencent Video main website and mobile APP (Android, iOS)
- Voov Meeting
- Tencent Cloud (computing/container and middleware/storage/network and CDN/security) (Refer to corresponding products in Tencent Cloud Product Overview - Tencent Cloud https://cloud.tencent.com/product)
- Tencent PC Manager / Tencent Mobile Manager
2. Other In-Scope Assets:
It includes the majority of Tencent's products and businesses, such as Tencent Game Helper (腾讯游戏助手), Tencent Ride Code Mini Program(腾讯乘车码小程序), QQ Music and other products, including but not limited to mobile applications, clients, mini programs, web sites, hardware, IoT, server services, and other product models.
3. *Notes about Tencent Cloud (cloud.tencent.com as included in *.tencent.com)
Only vulnerabilities affecting the platform itself and IP owned by Tencent will be accepted. If an IP belongs to Tencent Cloud external customer, it is not considered in scope.
Test Plan
You can use a QQ or Wechat account to log into all Tencent's products and services. 1. To register a QQ account, please go to https://ssl.zc.qq.com/v3/index-en.html?type=0 and follow the instructions. 2. To register a WeChat account, please download an WeChat app from App store or through Android system, then follow the registration guide. Once you have a QQ or WeChat account, you can start testing.
Out-of-Scope Vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope (either ineligible or false positives):
- "Self" XSS
- Session fixation
- Content Spoofing
- Missing cookie flags
- SSL/TLS best practices
- Mixed content warnings
- Clickjacking/UI redressing
- Flash-based vulnerabilities
- Admin panel can be brute force
- Local denial of service of Mobile APP
- Reflected file download attacks (RFD)
- Physical or social engineering attacks
- Feedback,comment,message,etc. flooding
- SMS/Email flooding for some of our business
- CSRF/XSS with long or unpredictable parameter
- Login/logout/unauthenticated/low-impact CSRF
- Unverified Results of automated tools or scanners
- No SPF/DMARC in non-email domains/subdomains
- Attacks requiring MITM or physical access to a user's device
- Issues related to networking protocols or industry standards
- Error information disclosure that cannot be used to make a direct attack
- Missing security-related HTTP headers which do not lead directly to a vulnerability
- Information leakage that cannot be used to make a direct attack,like server IP,server version,path,error message,internal IP,etc.
Detecting SSRF
We have set up a "demo" service for SSRF testing. If you believe you have an SSRF in production, please use either of the following IP/port combinations for testing:
This service will accept HTTP requests to any endpoint, of any request type, and will return a secret token in both headers and response body.
Out of scope
- Please note that the vulnerabilities reported for the following assets will not be eligible for bounties.
- *.qzoneapp.com
- *. myqcloud.com
- Third-party applications and websites
- *Notes about Tencent Cloud (cloud.tencent.com as included in *.tencent.com)
- Only vulnerabilities affecting the platform itself and IP owned by Tencent will be accepted. If an IP belongs to Tencent Cloud external customer, it is not considered in scope.
Qualifying vulnerabilities
- Cross-site Scripting (XSS)
- Cross-site Request Forgery (CSRF)
- Server-Side Request Forgery (SSRF)
- SQL Injection
- Remote Code Execution (RCE)
- XML External Entity Attacks (XXE)
- Access Control Issues (Insecure Direct Object Reference issues, etc.)
- Exposed Administrative Panels that without strong protection
- Directory Traversal Issues
- Local File Disclosure (LFD)
- Vast Users' Sensitive Information Leakage
- Vast Order details Leakage
Non-qualifying vulnerabilities
- "Self" XSS
- Session fixation
- Content Spoofing
- Missing cookie flags
- SSL/TLS best practices
- Mixed content warnings
- Clickjacking/UI redressing
- Flash-based vulnerabilities
- Admin panel can be brute force
- Local denial of service of Mobile APP
- Reflected file download attacks (RFD)
- Physical or social engineering attacks
- Feedback,comment,message,etc. flooding
- SMS/Email flooding for some of our business
- CSRF/XSS with long or unpredictable parameter
- Login/logout/unauthenticated/low-impact CSRF
- Unverified Results of automated tools or scanners
- No SPF/DMARC in non-email domains/subdomains
- Attacks requiring MITM or physical access to a user's device
- Issues related to networking protocols or industry standards
- Error information disclosure that cannot be used to make a direct attack
- Missing security-related HTTP headers which do not lead directly to a vulnerability
- Information leakage that cannot be used to make a direct attack,like server IP,server version,path,error message,internal IP,etc.