CVE-2017-7312

9.8 CRITICAL

📋 TL;DR

CVE-2017-7312 is an authentication bypass vulnerability in Personify360 e-Business software that allows unauthenticated attackers to access the /TabId/275 URI to add vendor accounts or read existing vendor data including usernames and passwords. This affects organizations using Personify360 e-Business versions 7.5.2 through 7.6.1 for vendor management.

💻 Affected Systems

Products:
  • Personify360 e-Business
Versions: 7.5.2 through 7.6.1
Operating Systems: Windows Server (typical deployment)
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all deployments with the vendor management module enabled. The vulnerability is in the web application layer and does not depend on specific OS configurations.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of vendor management system allowing attackers to create fraudulent vendor accounts, steal credentials, modify payment information, and potentially pivot to other systems using stolen credentials.

🟠

Likely Case

Unauthorized access to vendor account data leading to credential theft, financial fraud through vendor impersonation, and data exfiltration of sensitive business information.

🟢

If Mitigated

Limited impact with proper network segmentation, strong authentication controls, and monitoring that detects unauthorized access attempts to the vulnerable endpoint.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

The vulnerability requires no authentication and can be exploited with simple HTTP requests to the vulnerable endpoint. Public blog posts demonstrate the exploitation technique.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 7.6.2 or later

Vendor Advisory: https://personifycorp.com/security-advisories (historical advisory, may no longer be available)

Restart Required: Yes

Instructions:

1. Contact Personify support for patch files. 2. Backup current installation. 3. Apply patch following vendor instructions. 4. Restart application services. 5. Verify fix by testing access to /TabId/275.

🔧 Temporary Workarounds

Web Application Firewall Rule

all

Block access to the vulnerable /TabId/275 endpoint

WAF rule: DENY requests to */TabId/275*

Network Access Control

all

Restrict access to Personify360 application to authorized IPs only

Firewall rule: ALLOW only trusted IPs to TCP port 80/443

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate Personify360 from untrusted networks
  • Enable detailed logging and monitoring for all access attempts to /TabId/275 endpoint

🔍 How to Verify

Check if Vulnerable:

Attempt to access https://[personify-server]/TabId/275 without authentication. If you can view vendor data or add vendor accounts, the system is vulnerable.

Check Version:

Check Personify360 administration console or contact vendor support for version information

Verify Fix Applied:

After patching, attempt the same access. You should receive an authentication prompt or access denied error.

📡 Detection & Monitoring

Log Indicators:

  • HTTP 200 responses to /TabId/275 from unauthenticated users
  • Unusual vendor account creation events
  • Multiple failed authentication attempts followed by successful access to vendor endpoints

Network Indicators:

  • Unusual traffic patterns to /TabId/275 endpoint
  • HTTP GET/POST requests to vendor management URIs from unexpected IPs

SIEM Query:

source="personify-logs" AND (uri="/TabId/275" OR uri="*vendor*") AND user="anonymous"

🔗 References

📤 Share & Export