Skip to main content

Meatmeet Pro Thermometer CVE-2025-65828

MEDIUM
Missing Authentication for Critical Function (CWE-306)
2025-12-10 cve@mitre.org
6.5
CVSS 3.1 · Vendor: mitre
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Move within BLE radio range
  2. Delivery
    Enumerate thermometer GATT services
  3. Exploit
    Send unauthenticated clear-config BLE command
  4. Execution
    Device factory-resets and disassociates from owner account
  5. Persist
    Owner loses cloud temperature monitoring
  6. Impact
    Manual re-provisioning required to restore service

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The attacker must be within Bluetooth Low Energy radio range of the target device, typically 10-100 meters depending on environment and antenna strength. No pairing, bonding, PIN, or authentication credentials are required - the BLE management interface accepts shutdown, restart, and clear-config commands from any scanning BLE client. The device must be powered on and in an active (discoverable or connectable) BLE state. The clear-config impact is limited to cloud-connectivity disruption; physical food-safety monitoring via the thermometer probe itself may continue locally if the device restarts. Exploitation is limited to proximity attackers; remote internet-based exploitation is not possible given the BLE attack vector.

Impact

The CVSS 3.1 vector (AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) scores 6.5 and accurately reflects the attack characteristics: adjacent-network (BLE proximity, typically 10-100 meters), low complexity once in range, no privileges required, and high availability impact. EPSS of 0.27% at the 19th percentile is consistent with a niche consumer IoT product - the low score reflects limited deployment scale, not low reproducibility; the public POC demonstrates the technique is trivially applied. CISA KEV is absent, indicating no confirmed active exploitation campaigns at time of analysis. The clear-config function elevates practical impact beyond a simple reboot: a targeted victim must manually re-pair and re-configure the device to resume cloud connectivity, which is a meaningful disruption in a cooking or food-safety monitoring context. There is no confidentiality or integrity risk - the attack is purely disruptive. Physical proximity (BLE range) is the primary limiting factor for real-world exploitation, which meaningfully constrains mass targeting but does not prevent determined proximity attacks.

Exploit ScenarioDerived

An attacker within BLE range of a Meatmeet Pro thermometer - for example, a person standing outside a restaurant kitchen or adjacent apartment - uses the publicly available proof-of-concept gist to enumerate the device's BLE GATT services and sends an unauthenticated clear-config command. The thermometer immediately factory-resets, dissociating itself from the owner's account, and the owner loses all temperature monitoring and cloud alerts until they notice the device is offline, physically access it, and re-provision it through the companion app. A persistent attacker could repeat this on re-configuration to continuously deny service.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 05, 2026

Unauthenticated Bluetooth Low Energy (BLE) command execution against the Meatmeet Pro WiFi & Bluetooth Meat Thermometer firmware 1.0.34.4 allows any proximity attacker to issue shutdown, restart, or factory-reset commands without credentials, resulting in a denial of service. The clear-config command is particularly disruptive: it dissociates the device from its owner account, severing the connection to the Meatmeet cloud backend and requiring full device re-provisioning before temperature data can be received again. A public proof-of-concept is available via a GitHub gist, though EPSS sits at 0.27% (19th percentile), reflecting the niche consumer IoT footprint rather than low technical reproducibility.

RemediationAI

No vendor-released patch has been identified at time of analysis. There is no publicly available vendor advisory or fixed firmware version in the referenced sources. As a compensating control, users should store the thermometer in a physically controlled environment to limit BLE adjacency exposure - BLE range is typically 10-100 meters, so indoor use in a home or restaurant reduces but does not eliminate proximity attack surface. Disabling BLE discovery when active pairing is not in progress (if the firmware supports such a mode) would reduce the attack window; however, it is not confirmed whether firmware 1.0.34.4 supports this. Users affected by a clear-config attack must re-pair and re-configure the device through the companion app to restore cloud connectivity. Users should monitor the Meatmeet product page and firmware update channels for a patched release that enforces BLE authentication or pairing requirements before accepting management commands.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is the Meatmeet Pro WiFi & Bluetooth Meat Thermometer firmware at version 1.0.34.4 (CPE: cpe:2.3:o:meatmeet:meatmeet_pro_wifi_&_bluetooth_meat_thermometer_firmware:1.0.34.4). The device exposes a Bluetooth Low Energy (BLE) interface that accepts operational commands - including shutdown, restart, and clear config - without requiring any pairing PIN, bonding, or authentication handshake. CWE-306 (Missing Authentication for Critical Function) precisely captures the root cause: critical device-management functions are reachable over the BLE radio interface with no access control layer. BLE's default open-scanning model means any device within radio range can discover and interact with the thermometer's GATT service without prior pairing.

Know when Meatmeet Pro Wifi Bluetooth Meat Thermometer Firmware gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (mitre) PRIMARY 6.5 MEDIUM
AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI 6.5 MEDIUM

BLE proximity mandates AV:A; no auth required (PR:N); only availability disrupted with no confidentiality or integrity impact.

3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

DescriptionCVE.org

An unauthenticated attacker within proximity of the Meatmeet device can issue several commands over Bluetooth Low Energy (BLE) to these devices which would result in a Denial of Service. These commands include: shutdown, restart, clear config. Clear config would disassociate the current device from its user and would require re-configuration to re-enable the device. As a result, the end user would be unable to receive updates from the Meatmeet base station which communicates with the cloud services until the device had been fixed or turned back on.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Rare
niche consumer IoT meat thermometer, limited enterprise footprint
Exploit
POC
Public exploit code exists
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Controlled
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

52
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

Affected Products (CPE)CVE.org

cpe:2.3:o:meatmeet:meatmeet_pro_wifi_\&_bluetooth_meat_thermometer_firmware:1.0.34.4:*:*:*:*:*:*:*

References

Advisories & patches

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy