CVE-2024-28627

7.5 HIGH

📋 TL;DR

This vulnerability in Flipsnack allows a local attacker to access sensitive information through the reader.gz.js file. It affects Flipsnack users running the vulnerable version, potentially exposing confidential data to unauthorized local users.

💻 Affected Systems

Products:
  • Flipsnack
Versions: v.18/03/2024
Operating Systems: All platforms running Flipsnack
Default Config Vulnerable: ⚠️ Yes
Notes: Affects Flipsnack installations with the vulnerable reader.gz.js file present.

⚠️ 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

Complete exposure of sensitive application data, configuration files, or user information to local attackers, potentially leading to further system compromise.

🟠

Likely Case

Local information disclosure of application-specific sensitive data that could be used for reconnaissance or privilege escalation.

🟢

If Mitigated

Limited impact with proper access controls and file permissions restricting local user access to sensitive files.

🌐 Internet-Facing: LOW - This is a local attack vector requiring local system access.
🏢 Internal Only: MEDIUM - Internal users with local access could exploit this to gather sensitive information.

🎯 Exploit Status

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

Requires local access to the system. Exploitation involves accessing the vulnerable reader.gz.js file to extract sensitive information.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Version after v.18/03/2024

Vendor Advisory: https://www.flipsnack.com/

Restart Required: Yes

Instructions:

1. Check current Flipsnack version
2. Update to latest version from official Flipsnack sources
3. Restart Flipsnack services
4. Verify the reader.gz.js file no longer contains sensitive information

🔧 Temporary Workarounds

Restrict file permissions

linux

Set strict file permissions on reader.gz.js to prevent unauthorized local access

chmod 600 reader.gz.js
chown root:root reader.gz.js

Remove sensitive data from file

all

Sanitize the reader.gz.js file to remove any sensitive information

Review and clean sensitive data from reader.gz.js

🧯 If You Can't Patch

  • Implement strict access controls to limit local user access to Flipsnack directories
  • Monitor access to reader.gz.js file and alert on unauthorized access attempts

🔍 How to Verify

Check if Vulnerable:

Check if Flipsnack version is v.18/03/2024 and examine reader.gz.js file for sensitive information exposure

Check Version:

Check Flipsnack application version in admin interface or configuration files

Verify Fix Applied:

Verify Flipsnack version is updated beyond v.18/03/2024 and reader.gz.js no longer contains sensitive data

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized access attempts to reader.gz.js file
  • File read operations on sensitive Flipsnack files

Network Indicators:

  • Local file access patterns to Flipsnack directories

SIEM Query:

source="*flipsnack*" AND (file="*reader.gz.js*" OR action="read")

🔗 References

📤 Share & Export