Skip to main content

Use of uninitialized value $ua in index at /usr/local/cpanel/Cpanel/HTTP.pm line 183

Comments

11 comments

  • Andrew

    Where do you see them exactly? Right after logging in to WHM or in cPanel? under any submenus? Do you have enough space on the server? Do you use any custom theme etc..?

    Andrew N. - cPanel Plesk VMWare Certified Professional
    Do you need immediate assistance? 20 minutes response time!*
    EmergencySupport - Professional Server Management and One-time Services

    0
  • bloatedstoat

    We receive a report every hour that is compiled from the logs of individual service logs and cover the period over the previous hour. ie: Log compilation issued at 2pm covering events from 1pm - 2pm.

    One of the extracts lists events taken fromthe /usr/local/cpanel/logs/error_log and that is where the lines appear. At times there are around 40-50, at other times very few and sometimes there are none at all.

    0
  • Alex Fassas

    We are seeing the same in our /usr/local/cpanel/logs/error_log. 

    We are running Ubuntu 22.04.5 and cPanel 134.0.67. 

    This started Saturday, 10/31/2026 sometime after Noon (UTC -5).  We probably had been applying Wordpress plugin updates with WP Toolkit during this period of time.  I am not sure where to check for logs on WP Toolkit activities.

    0
  • cPRex Jurassic Moderator

    Those errors alone aren't very helpful, although they do indicate an issue of some sort.  What do you see in the cPanel logs right before those entries?  It's likely that something else failed that led to that error, so hopefully there'd be a record of that.

    0
  • Alex Fassas

    Here is a snippet from the /usr/local/cpanel/logs/error_log.

    [2026-11-02 10:40:31 -0500] info [cpsrvd] version 11.134.0.67 online
    [2026-11-02 10:40:31 -0500] warn [cpsrvd] pre-auth floor clamped low: calibrated=0.060s, target=0.100s (two_crypts=0.007s). Host may be I/O-saturated during cpsrvd
    startup or running an unusually fast crypt algorithm.
    ==> cpsrvd 11.134.0.67 started
    ==> cpsrvd: loading security policy....Done
    ==> cpsrvd: Setting up SSL support ... Done
    ==> cpsrvd: transferred port bindings: 10,11,12,18,3,4,5,6,7,8,9
    ==> cpsrvd: bound to ports
    [2026-11-02 10:44:23 -0500] info [cpsrvd] version 11.134.0.67 online
    [2026-11-02 10:44:23 -0500] warn [cpsrvd] pre-auth floor clamped low: calibrated=0.060s, target=0.100s (two_crypts=0.006s). Host may be I/O-saturated during cpsrvd
    startup or running an unusually fast crypt algorithm.
    Use of uninitialized value $ua in index at /usr/local/cpanel/Cpanel/HTTP.pm line 183.
    Use of uninitialized value $ua in index at /usr/local/cpanel/Cpanel/HTTP.pm line 183.
    Use of uninitialized value $ua in index at /usr/local/cpanel/Cpanel/HTTP.pm line 183.

    0
  • cPRex Jurassic Moderator

    Is that snippet from directly before the "Use of uninitialized value" error?  That just looks like a normal service restart to me.

    0
  • Alex Fassas

    Yes.  Snipped from the error_log file directly with no lines removed.  Previous occurences of this "uninitialized value" error lines all appear to be preceded by these same lines.

    We know that our version of cPanel has the issue with the "warn [cpsrvd] pre-auth floor clamped low:"  Those warnings have been going on for many weeks now WITHOUT this additional "unitialized value" log lines.

    Per your earlier response to the OP; we DID make some WP Toolkit updates to Wordpress sites on Saturday, 10/31/2026.  Wondering if some of those plugin updates are at the root of this.  How do we look back at what was updated via WP Toolkit?

    0
  • cPRex Jurassic Moderator

    I don't see how this would be related to WP Toolkit, especially since there's so few other reports.  It might be best to create a ticket so this can be examined directly on one of the affected systems.

    0
  • bloatedstoat

    Thanks cpRex.

    I didn't want to jump to any conclusions but here's what I think is happening here.

    On our server there's substantial automated HTTP scanning activity targeting the server through its cPanel and Webmail service subdomains.

    [2026-11-02 02:49:55 +1100] warn [cpaneld] Duplicate logaccess (GET /firebase-adminsdk.json HTTP/1.1):  at /usr/local/cpanel/Cpanel/Server/Logger.pm line 91.
        Cpanel::Server::Logger::logaccess(Cpanel::Server::Logger=HASH(0x42c4468)) called at /usr/local/cpanel/Cpanel/Server/Response.pm line 182
        Cpanel::Server::Response::send_response(Cpanel::Server::Response=HASH(0x432d2d0), Cpanel::Server::Response::Source::String=HASH(0x455b560)) called at /usr/local/cpanel/Cpanel/Server.pm line 2544
        Cpanel::Server::write_content_to_socket(Cpanel::Server=HASH(0x42c23b0), SCALAR(0x21ffd68), SCALAR(0x44f0e68)) called at /usr/local/cpanel/Cpanel/Server.pm line 3281
        Cpanel::Server::process_and_send_login_template(Cpanel::Server=HASH(0x42c23b0), "login", "HTTP/1.1 401 Access Denied\x{d}\x{a}Set-Cookie: cprelogin=no; HttpOnl"..., HASH(0x44f0760)) called at /usr/local/cpanel/Cpanel/Server.pm line 1371
        Cpanel::Server::badpass(Cpanel::Server=HASH(0x42c23b0), __CPANEL_HIDDEN__, __CPANEL_HIDDEN__, __CPANEL_HIDDEN__, 1) called at cpsrvd.pl line 1566
        cpanel::cpsrvd::handle_one_connection(3) called at cpsrvd.pl line 1220
        cpanel::cpsrvd::script() called at cpsrvd.pl line 471

    The requests originate from multiple external IP addresses and attempt to access common application configuration files, credentials, development endpoints and potentially vulnerable application resources.

    Examples:
    /proc/self/environ
    /proc/self/cgroup
    /static/..;/..;/..;/..;/proc/self/environ
    /api/system/fileView?file=/proc/self/environ

    Looking into this I've established that:

    • Apache handles HTTPS connections on port 443.
    • cPanel's cpsrvd daemon handles the dedicated cPanel, WHM and Webmail ports.
    • Requests recorded with the proxy identifier in cPanel's access log are service-subdomain requests.
    • Requests for arbitrary URLs are subsequently appearing in cPanel's authentication log as failed login attempts without usernames.

    At least one Duplicate logaccess warning can be directly correlated with an individual HTTP probe.

    The cPanel access log contains entries such as:

    35.205.67.156 proxy ... 443

    The proxy identifier is significant. In cPanel's logging format, it identifies requests associated with service subdomains.

    Examples include:

    • cpanel.example.com
    • whm.example.com
    • webmail.example.com

    These services allow users to access cPanel functionality through standard HTTPS port 443 rather than connecting directly to the dedicated service ports. This explains why Apache is listening on port 443 while the requests are also appearing in cPanel's authentication logs.

    The cPanel login log contains entries such as:

    FAILED LOGIN cpaneld: login attempt without username

    The requests are not necessarily attempts to access cPanel using legitimate credentials.
    Rather, the cPanel service is receiving HTTP requests for arbitrary resource paths and processing them through its authentication mechanism.
    Because no username is supplied, cPanel records the requests as failed login attempts.
    This explains why requests such as:

    GET /firebase-adminsdk.json HTTP/1.1

    appear under the cpaneld identifier rather than as conventional website application requests.

    Similar activity is recorded under webmaild.

    The distinction is the service handling the request, not necessarily the intention of the external scanner.

    Another notable observation is that several requests produce both 404 and 401 entries.

    Examples include:

    /sitemap.xml
    /.env.supabase
    /netlify.toml
    /graphql
    /debug
    /internal

    Possible explanations include separate requests, or different processing stages producing separate log entries. The logs do not establish which explanation is correct.

    Importantly, a 401 response indicates an authentication or access-control restriction. It does not establish that the requested resource exists.

    And so to the Undefined User-Agent Warning

    The original error was:

    Use of uninitialized value $ua in index at /usr/local/cpanel/Cpanel/HTTP.pm line 183.

    The variable $ua is consistent with a User-Agent value.

    One possibility is that an incoming request did not provide a usable User-Agent header.

    However I have yet to establish a direct relationship between this warning and the Firebase probe (outlined above) or the other scanning activity.

    In short, it's a symptom of automated vulnerability scanning where a bot with no user-agent header attempts to harvest credentials through a service subdomain, cpaneld handles the request through proxying behaviour and the null user-agent triggers the log line.

    We're also picking up similar scanning that triggers lines and lines of other argument warnings - this has been touched upon in other posts, one of them my own.

    https://support.cpanel.net/hc/en-us/community/posts/43277587966231-Apache-Proxy-cpanel-services-and-vulnerability-scanners

    https://support.cpanel.net/hc/en-us/community/posts/43150129994007-CPANEL-53195-External-requests-trigger-HTTP-500-via-cPanel-404-safelock-failure

    A few examples of most recent:

    cpsrvd b7ec3b5031e3: Missing required arguments! at /usr/local/cpanel/Cpanel/Server.pm line 2674, <GEN547> line 663.
    cpsrvd b7ec3b5031e3: Missing required arguments! at /usr/local/cpanel/Cpanel/Server.pm line 2674, <GEN546> line 1096.
    null user passed to hulk.pm can_login: info: Cpanel::Hulk
    [2026-11-02 20:23:17 +1100] warn [cpaneld] Duplicate logaccess (GET /assets../.env HTTP/1.1):  at /usr/local/cpanel/Cpanel/Server/Logger.pm line 91.
        Cpanel::Server::Logger::logaccess(Cpanel::Server::Logger=HASH(0x3b11ab0)) called at /usr/local/cpanel/Cpanel/Server/Response.pm line 182
        Cpanel::Server::Response::send_response(Cpanel::Server::Response=HASH(0x3b7d5e0), Cpanel::Server::Response::Source::String=HASH(0x3da5318)) called at /usr/local/cpanel/Cpanel/Server.pm line 2544
        Cpanel::Server::write_content_to_socket(Cpanel::Server=HASH(0x3b11c30), SCALAR(0x21ffd68), SCALAR(0x3d40df0)) called at /usr/local/cpanel/Cpanel/Server.pm line 3281
        Cpanel::Server::process_and_send_login_template(Cpanel::Server=HASH(0x3b11c30), "login", "HTTP/1.1 401 Access Denied\x{d}\x{a}Set-Cookie: cprelogin=no; HttpOnl"..., HASH(0x3d40730)) called at /usr/local/cpanel/Cpanel/Server.pm line 1371
        Cpanel::Server::badpass(Cpanel::Server=HASH(0x3b11c30), __CPANEL_HIDDEN__, __CPANEL_HIDDEN__, __CPANEL_HIDDEN__, 1) called at cpsrvd.pl line 1566
        cpanel::cpsrvd::handle_one_connection(3) called at cpsrvd.pl line 1220
        cpanel::cpsrvd::script() called at cpsrvd.pl line 471
    [2026-11-02 20:24:38 +1100] warn [webmaild] Duplicate logaccess (GET /serverless.yml HTTP/1.1):  at /usr/local/cpanel/Cpanel/Server/Logger.pm line 91.
    	Cpanel::Server::Logger::logaccess(Cpanel::Server::Logger=HASH(0x3b11ab0)) called at /usr/local/cpanel/Cpanel/Server/Response.pm line 182
    	Cpanel::Server::Response::send_response(Cpanel::Server::Response=HASH(0x3b7d5c8), Cpanel::Server::Response::Source::String=HASH(0x3e1cd30)) called at /usr/local/cpanel/Cpanel/Server.pm line 2544
    	Cpanel::Server::write_content_to_socket(Cpanel::Server=HASH(0x3b11c30), SCALAR(0x21ffd68), SCALAR(0x3d40f18)) called at /usr/local/cpanel/Cpanel/Server.pm line 3281
    	Cpanel::Server::process_and_send_login_template(Cpanel::Server=HASH(0x3b11c30), "login", "HTTP/1.1 401 Access Denied\x{d}\x{a}Set-Cookie: webmailrelogin=no; Ht"..., HASH(0x3d40fa8)) called at /usr/local/cpanel/Cpanel/Server.pm line 1371
    	Cpanel::Server::badpass(Cpanel::Server=HASH(0x3b11c30), __CPANEL_HIDDEN__, __CPANEL_HIDDEN__, __CPANEL_HIDDEN__, 1) called at cpsrvd.pl line 1665
    	cpanel::cpsrvd::handle_one_connection(11) called at cpsrvd.pl line 1220
    	cpanel::cpsrvd::script() called at cpsrvd.pl line 471

    Interestingly we're also seeing this on 'DNS Only' too.

    /usr/local/cpanel/logs/error_log:
    Use of uninitialized value $ua in index at /usr/local/cpanel/Cpanel/HTTP.pm line 183.

     

     

    0
  • cPRex Jurassic Moderator

    bloatedstoat - my only interesting thought on that is that the cPanel daemon itself handles connections on port 80 when nothing else is running there, which is why you'd see that on a DNSOnly system.

    0
  • bloatedstoat

    Looks like service subdomains may well be responsible for the noise with scanners hitting the service daemons. 

    I'm going to open a new thread as this could easily go off-topic despite there being a relationship to the original post.

    Thank you.

    0

Please sign in to leave a comment.