Vulnerabilities List

I ran a https://www.shodan.io/ check on my own server IP and it flagged some 7.5 risk factor vulnerabilities that are quite long standing. Can anyone else confirm they have the same?
It showed only 3 open ports 443,5060 and 6001 however these CVE’s are a little bit concerning.


2013(4)

CVE-2013-4365

7.5Heap-based buffer overflow in the fcgid_header_bucket_read function in fcgid_bucket.c in the mod_fcgid module before 2.3.9 for the Apache HTTP Server allows remote attackers to have an unspecified impact via unknown vectors.

CVE-2013-2765

5.0The ModSecurity module before 2.7.4 for the Apache HTTP Server allows remote attackers to cause a denial of service (NULL pointer dereference, process crash, and disk consumption) via a POST request with a large body and a crafted Content-Type header.

CVE-2013-0942

4.3Cross-site scripting (XSS) vulnerability in EMC RSA Authentication Agent 7.1 before 7.1.1 for Web for Internet Information Services, and 7.1 before 7.1.1 for Web for Apache, allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

CVE-2013-0941

2.1EMC RSA Authentication API before 8.1 SP1, RSA Web Agent before 5.3.5 for Apache Web Server, RSA Web Agent before 5.3.5 for IIS, RSA PAM Agent before 7.0, and RSA Agent before 6.1.4 for Microsoft Windows use an improper encryption algorithm and a weak key for maintaining the stored data of the node secret for the SecurID Authentication API, which allows local users to obtain sensitive information via cryptographic attacks on this data.

2012(3)

CVE-2012-4360

4.3Cross-site scripting (XSS) vulnerability in the mod_pagespeed module 0.10.19.1 through 0.10.22.4 for the Apache HTTP Server allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

CVE-2012-4001

5.0The mod_pagespeed module before 0.10.22.6 for the Apache HTTP Server does not properly verify its host name, which allows remote attackers to trigger HTTP requests to arbitrary hosts via unspecified vectors, as demonstrated by requests to intranet servers.

CVE-2012-3526

5.0The reverse proxy add forward module (mod_rpaf) 0.5 and 0.6 for the Apache HTTP Server allows remote attackers to cause a denial of service (server or application crash) via multiple X-Forwarded-For headers in a request.

2011(2)

CVE-2011-2688

7.5SQL injection vulnerability in mysql/mysql-auth.pl in the mod_authnz_external module 3.2.5 and earlier for the Apache HTTP Server allows remote attackers to execute arbitrary SQL commands via the user field.

CVE-2011-1176

4.3The configuration merger in itk.c in the Steinar H. Gunderson mpm-itk Multi-Processing Module 2.2.11-01 and 2.2.11-02 for the Apache HTTP Server does not properly handle certain configuration sections that specify NiceValue but not AssignUserID, which might allow remote attackers to gain privileges by leveraging the root uid and root gid of an mpm-itk process.

2009(2)

CVE-2009-2299

5.0The Artofdefence Hyperguard Web Application Firewall (WAF) module before 2.5.5-11635, 3.0 before 3.0.3-11636, and 3.1 before 3.1.1-11637, a module for the Apache HTTP Server, allows remote attackers to cause a denial of service (memory consumption) via an HTTP request with a large Content-Length value but no POST data.

CVE-2009-0796

2.6Cross-site scripting (XSS) vulnerability in Status.pm in Apache::Status and Apache2::Status in mod_perl1 and mod_perl2 for the Apache HTTP Server, when /perl-status is accessible, allows remote attackers to inject arbitrary web script or HTML via the URI.

2007(1)

CVE-2007-4723

7.5Directory traversal vulnerability in Ragnarok Online Control Panel 4.3.4a, when the Apache HTTP Server is used, allows remote attackers to bypass authentication via directory traversal sequences in a URI that ends with the name of a publicly available page, as demonstrated by a “/…/” sequence and an account_manage.php/login.php final component for reaching the protected account_manage.php page.

To check if your installed versions are patched against these CVEs, you can check the Debian Security Tracker .

https://security-tracker.debian.org/tracker/source-package/apache2

Currently I have the following version:
(The install was from the default VPBX image available)
VPBX 4.1.0-9
Asterisk 18.23.1
Debian 11 Bullseye

So there are vulnerabilities.
Should everyone be running updates - say at least once a month?
What is the best practice for doing this ?
The usual apt update and apt upgrade or something additional?

Any advice for ways to keep the system updated and secure?

I ran the v4 to v4.5 upgrade automated script and help my breath… thank goodness it actually worked without a hitch.

However I would still like to know how to keep the OS up to date in a way that can’t affect the VPX from working safely. If this was a different system, I would have just done it.

I am now on V4.5.0-7 with Asterisk 20.11.1 and Debian 12 Bookworm.

A side note… every time I reboot, I have to go into the master trunk, hit update and then do the save/refresh for incoming calls to start working… no idea why that would be.
And just discovered non of the statistics on the dashboard is updating and no graphs either. Yikes.
Update: Found fix for stats issue:
Edit the file /usr/share/vitalpbx/monitor/config.ini and change the value localhost to 127.0.0.1 in the [asterisk] section. Finally, restart the vpbx-monitor service. systemctl restart vpbx-monitor
That worked - so just left with master trunk not auto connecting on reboot issue.