CVE-2024-38480

4.0 MEDIUM

📋 TL;DR

The Piccoma mobile app for Android and iOS versions before 6.20.0 contains a hard-coded API key for an external service. This allows local attackers with access to the device to extract the API key, potentially enabling unauthorized access to the external service. App users are not directly affected, but the service provider faces credential exposure risk.

💻 Affected Systems

Products:
  • Piccoma mobile application
Versions: All versions prior to 6.20.0
Operating Systems: Android, iOS
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in the app binary itself, not dependent on device configuration.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers obtain the API key and use it to make unauthorized requests to the external service, potentially accessing sensitive data, incurring costs, or disrupting service functionality.

🟠

Likely Case

Local attackers extract the API key through reverse engineering or debugging, then use it for limited unauthorized API calls until the key is revoked.

🟢

If Mitigated

With proper monitoring and rate limiting on the external service, unauthorized usage is quickly detected and blocked with minimal impact.

🌐 Internet-Facing: LOW
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires local access to the device or app binary for reverse engineering. No authentication bypass needed once the key is extracted.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 6.20.0

Vendor Advisory: https://jvn.jp/en/jp/JVN01073312/

Restart Required: Yes

Instructions:

1. Update Piccoma app to version 6.20.0 or later via Google Play Store or Apple App Store. 2. Restart the app after update.

🔧 Temporary Workarounds

Restrict app installation sources

all

Only install Piccoma from official app stores to ensure you receive security updates.

Monitor external service usage

all

Service providers should implement API usage monitoring and anomaly detection for the exposed key.

🧯 If You Can't Patch

  • Uninstall the Piccoma app if not essential.
  • Contact the service provider to request API key rotation and implement additional authentication controls.

🔍 How to Verify

Check if Vulnerable:

Check app version in settings. If version is below 6.20.0, the app is vulnerable.

Check Version:

Android: Settings > Apps > Piccoma > App info. iOS: Settings > General > iPhone Storage > Piccoma

Verify Fix Applied:

Confirm app version is 6.20.0 or higher after update.

📡 Detection & Monitoring

Log Indicators:

  • Unusual API call patterns from unexpected locations or devices
  • Sudden increase in API usage from single key

Network Indicators:

  • Traffic analysis showing API calls using hard-coded credentials
  • Requests to external service from unauthorized clients

SIEM Query:

source="api_gateway" AND (key="piccoma_hardcoded_key" OR anomalous_request_pattern)

🔗 References

📤 Share & Export