CVE-2023-6916

7.2 HIGH

📋 TL;DR

CVE-2023-6916 is an information disclosure vulnerability where OpenAPI audit logs may contain sensitive data like credentials or tokens. This affects systems using vulnerable versions of software that implement OpenAPI endpoints with logging enabled. Attackers could leverage exposed information to gain unauthorized access.

💻 Affected Systems

Products:
  • Software implementing OpenAPI endpoints with audit logging
Versions: Specific versions depend on vendor implementation - check vendor advisories
Operating Systems: All platforms running affected software
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability manifests when OpenAPI endpoints are enabled with audit logging. The specific affected products are documented in the Nozomi Networks advisory.

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

Full system compromise through credential theft leading to privilege escalation and lateral movement across the network.

🟠

Likely Case

Exposure of sensitive API tokens or credentials allowing unauthorized API access and data exfiltration.

🟢

If Mitigated

Limited impact with proper log access controls and monitoring, though sensitive data may still be exposed in logs.

🌐 Internet-Facing: HIGH - Internet-facing systems with OpenAPI endpoints could have audit logs containing sensitive data accessible to attackers.
🏢 Internal Only: MEDIUM - Internal systems still risk credential exposure if logs are accessible to unauthorized internal users.

🎯 Exploit Status

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

Exploitation requires access to audit logs containing sensitive OpenAPI request data. No public exploit code identified.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check vendor-specific updates

Vendor Advisory: https://security.nozominetworks.com/NN-2023:17-01

Restart Required: Yes

Instructions:

1. Identify affected software versions. 2. Apply vendor-provided patches. 3. Restart services. 4. Verify audit logs no longer contain sensitive OpenAPI data.

🔧 Temporary Workarounds

Disable OpenAPI audit logging

all

Temporarily disable audit logging for OpenAPI endpoints to prevent sensitive data exposure

Configure audit settings to exclude OpenAPI endpoints from logging

Restrict log access

linux

Implement strict access controls on audit log files and directories

chmod 600 /var/log/audit.log
setfacl -m u:audit:r-- /var/log/audit.log

🧯 If You Can't Patch

  • Implement strict access controls on audit log storage and transmission
  • Enable encryption for audit log files and implement regular log review procedures

🔍 How to Verify

Check if Vulnerable:

Review audit logs for OpenAPI requests containing sensitive data like tokens or credentials

Check Version:

Check software version against vendor patched versions

Verify Fix Applied:

Confirm audit logs no longer contain sensitive OpenAPI request data after patch application

📡 Detection & Monitoring

Log Indicators:

  • Audit logs containing full OpenAPI request payloads with sensitive data
  • Unauthorized access attempts to audit log files

Network Indicators:

  • Unusual API access patterns following log file access

SIEM Query:

source="audit.log" AND "OpenAPI" AND ("token" OR "password" OR "credential")

🔗 References

📤 Share & Export