CVE-2025-3652

5.3 MEDIUM

📋 TL;DR

The Petlibro Smart Pet Feeder Platform contains an information disclosure vulnerability that allows attackers to access private audio recordings of other users. By exploiting sequential audio IDs and insecure API endpoints, unauthorized users can assign and retrieve audio files belonging to any device. This affects all users of Petlibro Smart Pet Feeder Platform versions up to 1.7.31.

💻 Affected Systems

Products:
  • Petlibro Smart Pet Feeder Platform
Versions: up to 1.7.31
Operating Systems: Not OS-specific - affects the cloud platform/service
Default Config Vulnerable: ⚠️ Yes
Notes: This is a cloud platform vulnerability affecting the backend API service, not the physical pet feeder devices themselves.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Mass privacy breach where all user audio recordings become accessible to attackers, potentially revealing sensitive conversations, home activities, or pet-related information that could be used for social engineering or blackmail.

🟠

Likely Case

Targeted privacy violations where attackers access specific users' audio recordings, compromising personal privacy and potentially exposing household routines or conversations.

🟢

If Mitigated

Limited impact with proper access controls and monitoring, where only authorized users can access their own recordings and suspicious API activity is detected and blocked.

🌐 Internet-Facing: HIGH
🏢 Internal Only: LOW

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires valid user authentication but then allows access to other users' data. The vulnerability is well-documented in public advisories.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.7.32 or later

Vendor Advisory: Not publicly available

Restart Required: No

Instructions:

1. Contact Petlibro support for updated platform version. 2. Upgrade to version 1.7.32 or later. 3. Verify the /device/deviceAudio/use endpoint now validates user ownership before allowing audio assignment.

🔧 Temporary Workarounds

API Endpoint Restriction

all

Implement server-side validation to ensure users can only assign audio recordings to devices they own

Not applicable - requires code changes

Rate Limiting and Monitoring

all

Implement rate limiting on audio API endpoints and monitor for unusual access patterns

Not applicable - requires infrastructure changes

🧯 If You Can't Patch

  • Implement strict access controls and audit logging for all audio-related API endpoints
  • Consider disabling the audio recording feature until a patch can be applied

🔍 How to Verify

Check if Vulnerable:

Test if you can access the /device/deviceAudio/use endpoint with arbitrary audio IDs and retrieve audio URLs not belonging to your devices

Check Version:

Check platform version in admin interface or contact Petlibro support

Verify Fix Applied:

Verify that the /device/deviceAudio/use endpoint now properly validates user ownership before allowing audio assignment operations

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed audio assignment attempts
  • Unusual patterns of audio ID requests
  • Access to audio files from unexpected user accounts

Network Indicators:

  • Unusual volume of requests to /device/deviceAudio/use endpoint
  • Sequential audio ID requests from single IP

SIEM Query:

source="api_logs" AND (uri="/device/deviceAudio/use" AND status=200) | stats count by user_id, audio_id

🔗 References

📤 Share & Export