LKDR Tech Blog
  • Home
  • Categories
    • penetration testing
      • WPScan I
      • WPScan II
    • systems integration
      • Onlyoffice
      • Cpanel & WHM
    • Hardening
      • Hardening I
      • Hardening II
  • Download
  • News
  • Contact Us


TLS Version 1.0 Protocol Detection

The TLS Version 1.0 Protocol Detection vulnerability is a security flaw in the TLS 1.0 protocol that allows an attacker to downgrade a secure connection to an insecure one. This can be done by sending a specially crafted message that the server will interpret as a request for TLS 1.0. Once the connection is downgraded, the attacker can exploit other vulnerabilities in TLS 1.0 to steal sensitive data or take control of the system.

Here are some of the attacks that can be exploited by the TLS Version 1.0 Protocol Detection vulnerability:

  • POODLE (Padding Oracle On Downgraded Legacy Encryption)
  • BEAST (Browser Exploit Against SSL/TLS)
  • CRIME (Compression Ratio Info-leak Made Easy)
  • FREAK (Factoring Attack on RSA-EXPORT Keys)
  • LOGJAM (Diffie-Hellman Key Exchange Weakness)

These attacks can be used to steal sensitive data. Moreover, they can also be used to take control of the system and perform other malicious actions. If you are concerned about the security of your web server, it is important to disable TLS 1.0 and use a more secure version of the protocol. You should also make sure that your server is up to date with the latest security patches.


Configuring Protocols

TLS plays a vital role in the implementation stack. TLS is a critical security protocol that is used to encrypt communications between clients and servers. TLS 1.2 and TLS 1.3 are the two latest versions of the Transport Layer Security (TLS) protocol and offer many advantages over their previous versions. TLS 1.2 is the most widely used version of the TLS protocol, but TLS 1.3 is gaining popularity. 
It has a dramatic increase in performance compared to its predecessor 1.2. Its speed and security capabilities made it mandatory to use in today’s world. Its main function of it is to provide an encrypted channel between the client (the web browser) and the server (the web server) on a public platform like the Internet. To set the secure encrypted channel, it is required to configure the TLS protocol at both ends.

It’s important to learn the version of the webserver which supports TLS 1.3 before heading towards enabling TLS 1.3 on popular web servers.
            Apache: v2.4.38 or above. 
            Nginx: v1.13 and above.     
            MySQL: 8.0.18 and above. 


1. Locate your server config file


After locating the server configuration file, you can open it using a text editor. Then, you should be able to see and insert the following line into the configuration file.


Apache: /etc/apache2/apache2.conf






Nginx: /etc/nginx/nginx.conf


2. Once you have found the server config file, you can open it with a text editor to view and add the following line to the configuration file.

# intermediate configuration
SSLProtocol             all -SSLv3 -TLSv1 -TLSv1.1
Here, the term 'all' signifies enabling all versions of TLS/SSL protocols. The '-' symbol denotes the instruction to deactivate the mentioned protocols.'-SSLv3 -TLSv1 -TLSv1.1' indicates the action of disabling support for specific protocols, namely SSLV3, TLS 1.1 and TLS 1.0.



REFERENCES

[1] https://www.tenable.com/plugins/nessus/104743

[2] https://thesecmaster.com/how-to-disable-tls-1-0-and-tls-1-1-on-windows-server/

[3] https://learn.microsoft.com/en-us/security/engineering/solving-tls1-problem]







How does it happen..?

The SSL Medium Strength Cipher Suites Supported vulnerability is a security risk that can occur when a server supports the use of medium-strength encryption ciphers. These ciphers are considered to be less secure than stronger ciphers, and they can be more easily broken by attackers.
 

One example of a medium-strength cipher is RC4, which was first developed in the 1980s. RC4 is a Symmetric cipher, which means that the same key is used to encrypt and decrypt data. RC4 is relatively fast, but it is also relatively weak. In 2013, researchers discovered a new attack against RC4 that could be used to break the cipher in a matter of hours.

If a server supports the use of medium-strength ciphers, then an attacker could potentially exploit this vulnerability to break the encryption and gain access to sensitive data. This could include passwords, credit card numbers, or other personal information.


Mitigation...

We will offer two approaches to address this vulnerability, and you can select the method that aligns with your specific environmentIf you employ a self-managed hosting solution with a Linux server, Method 1 is applicable. similarly, if you utilize hosting services provided by a service provider, Method 2 is suitable.


Method 1: On the Server side

You are required to configure your server to use strong ciphers. You can achieve this by making changes to the configuration file of the server.

  • Locate your server config file

The location of the server config file depends on the web server software you are using.
Here are some examples of where you can find the server config file for some popular server software.


Apache: /etc/apache2/apache2.conf
Nginx: /etc/nginx/nginx.conf

  • Identify strong ciphers 

You need to identify strong and recommended ciphers according to the software your server uses. Most providers of web server software offer official documentation to assist in configuring and enabling strong encryption ciphers.

Apache:https://httpd.apache.org/docs/trunk/ssl/ssl_howto.html

Alternatively, you have the option to use the Mozilla SSL Generator, which provides a recommended, standardized SSL configuration based on your particular web server version.

You have the option to input information about your server software and environment into the portal. In response, the portal will furnish you with a sample configuration file that aligns with the details you've provided
We will use the Apache configuration file generated by the Mozilla SSL generator for the remaining setup.
 
# generated 2023-08-22, Mozilla Guideline v5.7, Apache 2.4.41, OpenSSL 1.1.1k, intermediate configuration
# https://ssl-config.mozilla.org/#server=apache&version=2.4.41&config=intermediate&openssl=1.1.1k&guideline=5.7

# this configuration requires mod_ssl, mod_socache_shmcb, mod_rewrite, and mod_headers
<VirtualHost *:80>
    RewriteEngine On
    RewriteCond %{REQUEST_URI} !^/\.well\-known/acme\-challenge/
    RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=301,L]
</VirtualHost>

<VirtualHost *:443>
    SSLEngine on

    # curl https://ssl-config.mozilla.org/ffdhe2048.txt >> /path/to/signed_cert_and_intermediate_certs_and_dhparams
    SSLCertificateFile      /path/to/signed_cert_and_intermediate_certs_and_dhparams
    SSLCertificateKeyFile   /path/to/private_key

    # enable HTTP/2, if available
    Protocols h2 http/1.1

    # HTTP Strict Transport Security (mod_headers is required) (63072000 seconds)
    Header always set Strict-Transport-Security "max-age=63072000"
</VirtualHost>

# intermediate configuration
SSLProtocol             all -SSLv3 -TLSv1 -TLSv1.1
SSLCipherSuite          ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-CHACHA20-POLY1305
SSLHonorCipherOrder     off
SSLSessionTickets       off

SSLUseStapling On
SSLStaplingCache "shmcb:logs/ssl_stapling(32768)"
The text highlighted in yellow color is the recommended strong ciphers by Mozilla.
You can copy this content and insert it into your configuration file as in the sample file. 

Then restart the Apache service to apply the changes.

Note:
Do not replace your existing web server configuration file with the sample file produced by Mozilla. Retrieve the necessary information from the sample file and use it appropriately.



Method 2: from cPanel and WHM

Most cPanel & WHM-managed services use OpenSSL to provide secure connections between client software and the server. The following section lists the interfaces and options in cPanel & WHM that allow you to configure the protocol and cipher lists for services that use OpenSSL.

If you find that you only have access to the cPanel, you should reach out to your hosting service provider and request them to enhance your default web service configuration with strong ciphers. You can guide the hosting service administrator by suggesting the steps below. However, if you have access to the WHM, you can proceed with the following modifications.

Go to  WHM ➝ Home ➝ Service Configuration ➝ cPanel Web Services Configuration



Replace TLS/SSL Cipher List with recommended and strong ciphers and then save the changes.
(If you have a list of medium-strength ciphers, you can exclude them from this list. There's no need to replace the default ciphers)



REFERENCES

[1] https://www.tenable.com/plugins/nessus/42873

[2] https://www.papercut.com/kb/Main/SSLCipherConfiguration/

[3] https://docs.cpanel.net/knowledge-base/security/how-to-update-ciphers-and-tls-protocols/

[4] https://ssl-config.mozilla.org/


























Ransomware attacks have grown up exponentially amid COVID-19, as cybercriminals take advantage of the new work-from-home world and target vulnerable industries and populations.

Ransomware penetrates an organization’s IT infrastructure through phishing emails or endpoint vulnerabilities and then encrypts files, holding data hostage until a fee is paid to decrypt them. The FBI has deemed ransomware the fastest growing malware threat, causing significant revenue loss, business downtime and reputational damage.

Therefore,  Protect Your Network From Ransomware by following the best practices below.


1. Backup files regularly

Backup all important files on regularly basis to an offsite server is recommended. Automatic backup systems of operating Systems(Windows , Linux) can be used for this purpose to backup data on daily basis.

For any sensitive data , ensure the backed-up data is encrypted to prevent data theft.


2. Security awareness programs for employees

Awareness sessions for employees to improve level of knowledge regarding information security. could be one of the best forms of defense.

Such sessions should focus on ;

  • Introduction about ransomware 
  • How to identify ransomware or if a machine is infected
  • Further steps - if a suspected ransomware attack is identified in office or work from home environment.
  • prevention tips for ransomware


3. Use of EDR(Endpoint Detection and Response) solution for endpoint protection.

EDR solution provide facility to manage security of the end points with proactive threat hunting and response. Advance EDR solutions provide Machine learning, Deep Learning based methodologies to accurate threat hunting. In addition Device control such as USB storage control, Network firewall for end points, system lock down or isolation facilities, sandboxing features are provided with the EDR.


4. Segment the System/Network

Segmenting  the Network will help to  reduce spreading a threat across the entire network. We can keep critical servers and application  in an isolated separate network to limit the spread.


5. Apply updates and patches regularly and promptly


Systems, applications and devices should be updated to the  latest version from reliable source. This will ensure the  system Security without exposing    security weaknesses  to attackers.


6. Proper use of login credentials.

Ensure that no easy platform is provide for ransomware or other malware by following best practices when login in to systems or handling credentials.

  • Do not use superuser/root user account to login to the system or server.
  • Use a regular non-admin account for web browsing, opening documents, and regular work.
  • When sending user login to someone use 2 different communication channels (email,SMS,Messenger,WhatsApp ...) to send username/login and password. And send it without mentioning keyword like “username” ,”password” ,”login” etc.



REFERENCES:
[1]https://www.techcert.lk/en/knowledge-base
[2]https://www.justice.gov/criminal-ccips/file/872771/download
[3] https://go.tenable.com

 


 Security risk: Critical 

Vulnerability: Drupal core - Critical - Third-party librariesThe Drupal project uses the pear Archive_Tar library, which has released a security update that impacts Drupal.

The vulnerability is mitigated by the fact that Drupal core's use of the Archive_Tar library is not vulnerable, as it does not permit symlinks.

Exploitation may be possible if contrib or custom code uses the library to extract tar archives (for example .tar, .tar.gz, .bz2, or .tlz) which come from a potentially untrusted source.

This advisory is not covered by Drupal Steward( is a web application firewall that bridges the gap between the time when a security release is announced and when your site is fully updated with the new security patch).

 

Solution: 

Install the latest version:

  • If you are using Drupal 9.2, update to Drupal 9.2.2.
  • If you are using Drupal 9.1, update to Drupal 9.1.11.
  • If you are using Drupal 8.9, update to Drupal 8.9.17.
  • If you are using Drupal 7, update to Drupal 7.82.

Versions of Drupal 8 prior to 8.9.x and versions of Drupal 9 prior to 9.1.x are end-of-life and do not receive security coverage.

 -published by https://www.drupal.org

MySQL brands itself as the world’s most popular open source database. As popular as MySQL database is among developers and SQL enthusiasts, it is equally popular amongst hackers. In today's article, you’ll learn some tips and tricks for securing your MySQL or MariaDB databases 

        1.Remove Users Without Password

    There are already created users, some of  some of which can connect to the database without a password or, even worse, anonymous users.This has changed in MySQL 5.7 which, by default, comes only with a root account that uses the password you choose at installation time. Still, there are MySQL installations which were upgraded from previous versions and these installations keep the legacy users. Also, MariaDB 10.2 on Centos-7 comes with anonymous users. Please note that users with very simple passwords are almost as insecure as users without any password. Passwords like “password” or “qwerty” are not really helpful.

    2.  Change default port mappings

    MySQL by default runs on port 3306. This should be changed after installation to obfuscate what critical services are running on which ports, as attackers will initially attempt to exploit default values.

    3.Do not run MySQL with root level privileges

    MySQL should be run under a specific, newly-created user account with the necessary permissions to run the service, as opposed to directly as the root user. This adds some auditing and logging benefits while preventing attackers from gaining access by hijacking the root user account.

    4. Limit or disable SHOW DATABASES

    Again, stripping remote attackers of their information gathering capabilities is critical to a secure security posture. For this reason, the SHOW DATABASES command should be limited or removed entirely by adding skip-show-database to the [mysqld] section of the MySQL configuration file at /etc/my.cnf.
     
     
     
     
    References:
    [1] https://www.upguard.com/blog/top-11-ways-to-improve-mysql-security
    [2] https://severalnines.com/database-blog/ten-tips-how-achieve-mysql-and-mariadb-security

     

     

Older Posts Home

ABOUT US

We are LK Domain Registry and we are happy to share our technical blog with you to explore knowledge.

Popular Posts

  • How to install Proxmox Mail Gateway
        Proxmox Mail Gateway is one of the leading open-source email security solution which helps to protect mail server against many email thr...
  • Oracle WebLogic Remote Code Execution Vulnerability Exploited
    Oracle web logic server is a Java EE application server that is part of Oracle’s Fusion Middleware portfolio and supports a variety of popul...
  • Remote Code Execution Vulnerability Patched in Drupal
    Drupal is an open-source content management system and successful exploitation of this vulnerability could allow for remote code execution. ...
  • Exploring Joomla CMS vulnerabilities-JoomScan
    JoomScan is an open source security scanner, developed with the aim of automating the task of vulnerability detection and reliability assura...

SUBSCRIBE & FOLLOW

Followers

Categories

  • ELK Stak 1
  • Hardening 4
  • Joomla 1
  • Oracle 1
  • Systems Integrations 3
  • WPScan 2

Total Pageviews

Contributors

  • Harsha Saparamadu
  • Isiwara Kumarage
  • Piushan Prasanga Perera
  • Sameera Dasanayake
  • Sampath Hennayake
  • Uththara Wijayamanna

Designed by OddThemes | Distributed by Gooyaabi Templates