
CVE-2023-46747: Critical Authentication Bypass Vulnerability in F5 BIG-IP Configuration Utility
A critical authentication bypass vulnerability (CVE-2023-46747) in the F5 BIG-IP Traffic Management User Interface affects versions 13.1.0-17.1.0. This vulnerability, with a CVSS score of 9.8, enables unauthenticated remote code execution through the configuration utility and poses severe risks to enterprise network infrastructure.
Reading Time: 8 minutes
TL;DR
- CVE-2023-46747 is a critical authentication bypass in F5 BIG-IP TMUI, allowing unauthenticated remote code execution with root privileges.
- Exploitation uses AJP request smuggling, manipulating remote_user and REMOTEROLE headers to bypass authentication.
- Successful attacks can lead to command execution via tmsh, persistence, and lateral movement across enterprise networks.
- Immediate patching, network segmentation, and monitoring TMUI/tmsh activity are essential to mitigate the risk.
- AccuKnox complements patching by enforcing workload-level policies, tracking secrets, monitoring activity, and capturing immutable runtime evidence for faster detection and investigation.
F5 BIG-IP systems face one of their most severe security threats with CVE-2023-46747, a critical authentication bypass vulnerability that has earned the maximum CVSS score of 9.8. This flaw in the Traffic Management User Interface (TMUI) allows attackers to execute remote code as root without any authentication, making it a prime target for cybercriminals and initial access brokers worldwide.
The vulnerability exploits Apache JServ Protocol (AJP) request smuggling techniques to bypass authentication controls entirely. Given the widespread deployment of F5 BIG-IP appliances in enterprise environments, this security flaw represents a significant risk to organizational infrastructure and requires immediate attention from security teams.
Understanding the Technical Foundation of CVE-2023-46747
Root Cause Analysis
CVE-2023-46747 stems from a fundamental design flaw in how F5 BIG-IP’s TMUI component processes Apache JServ Protocol requests. The vulnerability exists in the binary parsing logic that handles AJP traffic differently from standard HTTP requests, creating a security gap that attackers can exploit.
The core issue lies in the improper validation of AJP headers, specifically the remote_user and REMOTEROLE parameters. When the system receives malformed AJP requests, it fails to authenticate the source properly, allowing malicious actors to impersonate legitimate administrative users.
Apache JServ Protocol Exploitation Mechanics
AJP smuggling represents a sophisticated attack methodology that leverages the binary nature of the Apache JServ Protocol. This technique exploits discrepancies in how different system components interpret protocol specifications, enabling attackers to “smuggle” malicious requests past security controls.
The attack requires precise payload construction:
- Crafted POST requests containing exactly 0x204 bytes of data
- Manipulation of the remote_user parameter to “admin”
- Injection of REMOTEROLE header with value “0”
- Targeting of the TMUI AJP connector on TCP port 8009
This binary protocol manipulation bypasses traditional web application security measures because AJP operates at a lower level than HTTP and often lacks robust security validation mechanisms.
Attack Surface and Prerequisites
Successful exploitation requires network access to either:
- BIG-IP management ports
- Self-IP addresses where TMUI is exposed
- Internal network segments with AJP connector access
Once network connectivity is established, the vulnerability becomes trivially exploitable, requiring no specialized tools or advanced technical knowledge.
Exploitation Methodology and Attack Patterns
Multi-Stage Attack Process
The exploitation of CVE-2023-46747 follows a predictable attack chain that demonstrates the vulnerability’s critical nature:

Vulnerability Chaining Techniques
CVE-2023-46747 is frequently combined with other F5 BIG-IP vulnerabilities to maximize attack impact:
- CVE-2022-26377: Previous vulnerability that left AJP attack surfaces exposed
- CVE-2023-46748: SQL injection vulnerability enabling further privilege escalation
- Legacy authentication bypasses: Older vulnerabilities that compound the security risk
This chaining approach allows attackers to establish multiple persistence mechanisms and increases the likelihood of maintaining access even if some vulnerabilities are patched.
Real-World Threat Landscape and Active Exploitation
Initial Access Broker Operations
Security researchers have documented extensive exploitation of CVE-2023-46747 by initial access brokers who specialize in compromising enterprise networks for resale to other cybercriminal groups. These operations demonstrate the vulnerability’s value in the underground economy.
Key characteristics of observed attacks include :
- Automated scanning for vulnerable F5 BIG-IP systems
- Rapid exploitation following successful identification
- Deployment of multiple persistence mechanisms
- Sale of access credentials on dark web marketplaces
Advanced Persistent Threat Activity
Sophisticated threat actors, including groups tracked as UNC5174, have incorporated CVE-2023-46747 into broader exploitation campaigns. These actors often target multiple vulnerabilities simultaneously, creating comprehensive initial access operations that are difficult to detect and remediate.
The vulnerability’s appeal to advanced threat actors stems from:
- High success rate due to straightforward exploitation
- Immediate root-level access to critical infrastructure
- Low detection probability during initial compromise
- Extensive post-exploitation opportunities
Exploitation Timeline and Trends
Following the public disclosure of CVE-2023-46747, security researchers observed a significant increase in scanning and exploitation attempts. The availability of proof-of-concept code accelerated both defensive and offensive activities, with malicious actors quickly adapting the technical details for operational use.
Comprehensive Remediation and Mitigation Strategies
Primary Patch Management Approach
F5 has released comprehensive security updates addressing CVE-2023-46747 across affected product versions. Organizations must prioritize the application of these patches as the primary remediation strategy.
Critical patching considerations include:
- Version compatibility: Ensure patch compatibility with existing configurations
- Testing requirements: Conduct thorough testing in non-production environments
- Rollback procedures: Maintain documented rollback capabilities
- Change management: Follow established change control processes
Interim Mitigation Measures
For organizations unable to immediately apply patches, F5 has provided temporary mitigation scripts with specific implementation requirements:
Script Deployment Guidelines:
- Only use on BIG-IP versions 14.1.0 and later
- Thoroughly test in controlled environments before production deployment
- Monitor system performance and stability post-implementation
- Document all mitigation steps for future reference
Important Limitations:
- Mitigation scripts may impact system performance
- Temporary measures do not provide complete protection
- Scripts must not be used on versions prior to 14.1.0 due to stability risks
Detection and Monitoring Strategies
Organizations should implement comprehensive monitoring capabilities to detect potential exploitation attempts:

Network-Level Monitoring:
- AJP traffic pattern analysis
- Unusual administrative account creation activities
- Abnormal command execution patterns
- Suspicious network connections from BIG-IP systems
System-Level Monitoring:
- Administrative privilege escalation events
- Unauthorized configuration changes
- Unusual process execution patterns
- File system modifications in critical directories
Log Analysis Requirements:
- Centralized log collection from all F5 BIG-IP systems
- Automated correlation of security events
- Real-time alerting for suspicious activities
- Historical analysis capabilities for forensic investigation
Post-Exploitation Forensic Considerations
Evidence Collection and Analysis
Organizations that suspect CVE-2023-46747 exploitation must conduct thorough forensic analysis to determine the scope of compromise:
Critical Evidence Sources:
- TMUI access logs and authentication records
- System command history and execution logs
- Network traffic captures during suspected compromise timeframes
- File system changes and unauthorized modifications
- Administrative account creation and modification records
Forensic Analysis Priorities:
- Timeline reconstruction of attack activities
- Identification of persistent backdoors or malware
- Assessment of data exfiltration activities
- Evaluation of lateral movement attempts
Recovery and Hardening Measures
Complete recovery from CVE-2023-46747 exploitation requires comprehensive remediation efforts:
System Restoration Steps:
- Isolate affected systems from network access
- Conduct complete forensic imaging before remediation
- Apply all available security patches
- Remove unauthorized accounts and access mechanisms
- Reset all administrative credentials
- Restore systems from known-good backups if necessary
Security Hardening Requirements:
- Implement network segmentation for management interfaces
- Deploy additional monitoring and intrusion detection systems
- Establish regular security assessment schedules
- Enhance access controls and authentication mechanisms
Strategic Security Implications and Future Considerations

CVE-2023-46747 represents more than an isolated security vulnerability; it highlights fundamental challenges in enterprise infrastructure security. The ease of exploitation combined with the critical nature of F5 BIG-IP appliances creates significant organizational risk that extends beyond technical remediation.
Organizational Risk Assessment
The vulnerability’s impact on organizational security posture requires comprehensive evaluation:
Business Impact Considerations:
- Service availability during patching windows
- Regulatory compliance implications
- Customer data protection requirements
- Business continuity planning needs
Long-Term Security Strategy:

- Vulnerability management program effectiveness
- Incident response capability assessment
- Security architecture review requirements
- Third-party risk management evaluation
Check out the AccuKnox Vulnerability Use Case: Learn how the Rule Engine automates vulnerability prioritization, triggers alerts, and enforces runtime controls to reduce risk while you patch.
Industry-Wide Security Lessons
The active exploitation of CVE-2023-46747 by initial access brokers demonstrates the evolving threat landscape where sophisticated actors quickly weaponize newly disclosed vulnerabilities. This trend requires organizations to maintain rapid response capabilities and comprehensive security monitoring.
The vulnerability also underscores the importance of defense-in-depth strategies that can mitigate the impact of authentication bypass vulnerabilities through additional security controls and monitoring capabilities.
How AccuKnox Helps During CVE-2023-46747 Response

AccuKnox offers useful security measures that help reduce the risks linked to CVE-2023-46747
- Workload-level policy enforcement: Restrict access to critical management interfaces and the TMUI AJP connector to prevent unauthorized connections.
- Monitoring TMUI and tmsh activity: Detect unusual commands, privilege escalation attempts, or administrative actions that could indicate exploitation.
- Secrets and credential tracking: Observe access patterns for service account tokens, configuration secrets, and credentials to catch abnormal activity.
- Correlation of network, host, and configuration telemetry: Generate high-confidence alerts by combining multiple data sources for clear visibility of suspicious behavior.
- Immutable runtime evidence for forensics: Capture tamper-proof logs of activity to accelerate investigation and reconstruct attack timelines.
These capabilities help organizations contain exploitation, detect attacks early, and maintain secure operations while applying official F5 patches.
Conclusion

CVE-2023-46747 highlights the severe risk posed by authentication bypass vulnerabilities in widely deployed enterprise appliances. With the potential for unauthenticated remote code execution, immediate patching, monitoring, and access controls are critical.
By combining F5 patches with runtime security provided by AccuKnox, organizations gain:
- Real-time visibility into TMUI and tmsh activity
- Enforcement of workload-level policies to limit attack vectors
- Rapid detection and containment of suspicious behavior
- Immutable evidence to accelerate forensic investigations
Proactively safeguard your F5 BIG-IP deployments: implement patches and strengthen runtime controls with AccuKnox. Schedule a demo to see how these protections work in practice.
FAQs
1. What is CVE-2023-46747?
CVE-2023-46747 is a critical authentication bypass vulnerability in F5 BIG-IP’s Traffic Management User Interface (TMUI) that allows unauthenticated attackers to execute remote code with root privileges.
2. Which F5 BIG-IP versions are affected?
This vulnerability affects F5 BIG-IP versions 13.1.0 through 17.1.0.
3. How is the vulnerability exploited?
Attackers exploit CVE-2023-46747 using Apache JServ Protocol (AJP) request smuggling, manipulating the remote_user and REMOTEROLE headers to bypass authentication and execute commands via tmsh.
4. What are the mitigation steps for CVE-2023-46747?
Organizations should apply F5 patches immediately, implement network-level segmentation, monitor TMUI and tmsh activity, track secret access, and consider runtime controls like AccuKnox to detect and contain exploitation.
5. How can AccuKnox help protect against this vulnerability?
AccuKnox enforces workload-level policies, monitors TMUI/tmsh activity, tracks secret access, correlates telemetry for high-confidence alerts, and captures immutable runtime evidence to detect attacks and accelerate investigations while patches are applied.
Get a LIVE Tour
Ready for a personalized security assessment?
“Choosing AccuKnox was driven by opensource KubeArmor’s novel use of eBPF and LSM technologies, delivering runtime security”

Golan Ben-Oni
Chief Information Officer
“At Prudent, we advocate for a comprehensive end-to-end methodology in application and cloud security. AccuKnox excelled in all areas in our in depth evaluation.”

Manoj Kern
CIO
“Tible is committed to delivering comprehensive security, compliance, and governance for all of its stakeholders.”

Merijn Boom
Managing Director




