☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]

CVE-2024-47150

CVE-2024-47150 Information Disclosure in Honor
📅 PUBLISHED: 2024-12-26 12:16 UTC 🔄 UPDATED: 2026-08-12 14:51 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: Public
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.10%
👁️
0.10% probability
2.5× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
Country: China License: Commercial
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS SEVERITY SCALE
9.0–10.0 CRITICAL
7.0–8.9 HIGH
4.0–6.9 MEDIUM
0.1–3.9 LOW
0.0 NONE
3.3
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2024-47150 is a low-severity information leak vulnerability affecting certain Honor products. The vulnerability allows an attacker to leak sensitive information from the device, potentially exposing user data or system details. The CVSS score is 3.3, indicating a low risk, but the lack of a patch and limited public information increases the potential impact for targeted attacks. No proof-of-concept (PoC) code, exploit templates, or patch details are currently available. The vulnerability is not related to any open-source package ecosystem (NPM, PyPI, Go, Ruby).

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

CVSS Breakdown & Threat Level

  • CVSS Score: 3.3 (Low)
  • Vector: UNKNOWN (No vector string provided)
  • Attack Vector: Likely local or adjacent network (based on low score)
  • Attack Complexity: Likely low
  • Privileges Required: Likely low or none
  • User Interaction: Likely none
  • Scope: Unchanged
  • Confidentiality Impact: Low (information leak)
  • Integrity Impact: None
  • Availability Impact: None
  • Threat Level: Low (EPSS 0.0%, no known exploits)

Deep Dive & Mechanics

The vulnerability is described as an information leak in Honor products. Without specific technical details, the likely mechanism involves improper handling of sensitive data during device operations, such as:

  • Insecure storage of credentials or tokens.
  • Exposure of system logs or debug information.
  • Leakage of device identifiers or user data through unencrypted channels.
  • Improper access control to device APIs or local resources.

The attack surface is limited to local or adjacent network access, requiring the attacker to have some level of access to the device or its network.

Vulnerable vs. Patched Code

No code samples are available because the vulnerability details are not public. The vendor has not released a patch, and no open-source references exist.

Exploitation & Lab Setup

No exploit code or PoC is publicly available. The following sections provide general guidance for testing and defense.

Red Team

  • Reconnaissance: Identify Honor devices on the network using Shodan dorks: "Honor device" or "Honor information leak".
  • Exploitation Attempt: If a device is found, attempt to access debug endpoints, read local files, or intercept unencrypted traffic. Example command to test for exposed logs:
    curl http://<device-ip>/debug/logs
    
  • Data Exfiltration: If successful, capture leaked data (e.g., tokens, device info) and exfiltrate via a controlled channel.

Blue Team

  • Monitor Network Traffic: Look for unusual outbound connections from Honor devices to unknown IPs.
  • Check Device Logs: Review device logs for unauthorized access attempts or unexpected data transfers.
  • Isolate Devices: Place Honor devices on a separate VLAN with strict access controls.
  • Apply Workarounds: If possible, disable unnecessary services or restrict access to debug interfaces.

Indicators of Compromise (IOCs)

  • Network: Unusual outbound connections from Honor devices to IPs not in the allowlist.
  • File: Presence of unexpected log files or debug output on the device.
  • Behavior: Device sending sensitive data (e.g., tokens, serial numbers) over unencrypted channels.

Detection Engineering

YARA Rule

rule CVE_2024_47150_Honor_Info_Leak {
    meta:
        description = "Detects potential information leak from Honor devices"
        author = "Valters IT"
        date = "2025-04-10"
        reference = "CVE-2024-47150"
    strings:
        $s1 = "Honor" nocase
        $s2 = "debug" nocase
        $s3 = "token" nocase
        $s4 = "password" nocase
    condition:
        any of ($s*) and filesize < 10MB
}

Sigma Rule

title: Honor Device Information Leak Detection
id: cve-2024-47150
status: experimental
description: Detects network traffic indicative of information leak from Honor devices
author: Valters IT
date: 2025-04-10
logsource:
    category: network_connection
    product: windows
detection:
    selection:
        DestinationPort: 80
        DestinationHostname: "*honor*"
        PayloadContains: "token"
    condition: selection
falsepositives:
    - Legitimate device updates
level: low

Suricata Rule

alert tcp $HOME_NET any -> $EXTERNAL_NET 80 (msg:"CVE-2024-47150 Honor Information Leak"; content:"Honor"; nocase; content:"token"; nocase; distance:0; within:100; sid:1000001; rev:1;)

Remediation & Mitigation

  • Vendor Patch: No patch available. Monitor Honor’s security advisories for updates.
  • Workarounds:
    • Disable unnecessary services on the device.
    • Restrict network access to the device using firewall rules.
    • Use a VPN or encrypted tunnel for device communication.
    • Regularly audit device logs for suspicious activity.
  • Long-term: Replace affected devices with patched alternatives if available.

Valters IT

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

Honor device
Honor information leak

💣 PoC CODE AVAILABLE

Exploit code for this CVE is tracked in our database. Access poc_code via API Pro.

[ API_PRO ] →
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2024-47150/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.