Uploaded image for project: 'Rules Repository'
  1. Rules Repository
  2. RSPEC-4792

Configuring loggers is security-sensitive



    • Message:
      Make sure that this logger's configuration is safe.
      Make sure that this logger's configuration is safe.
    • Highlighting:

      Call to logger configuration function.

      Call to logger configuration function.
    • Default Severity:
    • Impact:
    • Likelihood:
    • Default Quality Profiles:
      Sonar way
    • Targeted languages:
      ABAP, APEX, C, C++, Cobol, Flex, Go, JavaScript, Kotlin, Objective-C, RPG, Ruby, Rust, Scala, Swift, T-SQL, TypeScript, VB6
    • Covered Languages:
      C#, Java, PHP, Python, VB.Net
    • Irrelevant for Languages:
      CSS, HTML, XML
    • Analysis Scope:
      Main Sources
    • Common Rule:
    • CWE:
    • OWASP:
    • SANS Top 25:
      Porous Defenses


      Configuring loggers is security-sensitive. It has led in the past to the following vulnerabilities:

      Logs are useful before, during and after a security incident.

      • Attackers will most of the time start their nefarious work by probing the system for vulnerabilities. Monitoring this activity and stopping it is the first step to prevent an attack from ever happening.
      • In case of a successful attack, logs should contain enough information to understand what damage an attacker may have inflicted.

      Logs are also a target for attackers because they might contain sensitive information. Configuring loggers has an impact on the type of information logged and how they are logged.

      This rule flags for review code that initiates loggers configuration. The goal is to guide security code reviews.

      Ask Yourself Whether

      • unauthorized users might have access to the logs, either because they are stored in an insecure location or because the application gives access to them.
      • the logs contain sensitive information on a production server. This can happen when the logger is in debug mode.
      • the log can grow without limit. This can happen when additional information is written into logs every time a user performs an action and the user can perform the action as many times as he/she wants.
      • the logs do not contain enough information to understand the damage an attacker might have inflicted. The loggers mode (info, warn, error) might filter out important information. They might not print contextual information like the precise time of events or the server hostname.
      • the logs are only stored locally instead of being backuped or replicated.

      There is a risk if you answered yes to any of those questions.

      Recommended Secure Coding Practices

      • Check that your production deployment doesn't have its loggers in "debug" mode as it might write sensitive information in logs.
      • Production logs should be stored in a secure location which is only accessible to system administrators.
      • Configure the loggers to display all warnings, info and error messages. Write relevant information such as the precise time of events and the hostname.
      • Choose log format which is easy to parse and process automatically. It is important to process logs rapidly in case of an attack so that the impact is known and limited.
      • Check that the permissions of the log files are correct. If you index the logs in some other service, make sure that the transfer and the service are secure too.
      • Add limits to the size of the logs and make sure that no user can fill the disk with logs. This can happen even when the user does not control the logged information. An attacker could just repeat a logged action many times.

      Remember that configuring loggers properly doesn't make them bullet-proof. Here is a list of recommendations explaining on how to use your logs:

      • Don't log any sensitive information. This obviously includes passwords and credit card numbers but also any personal information such as user names, locations, etc... Usually any information which is protected by law is good candidate for removal.
      • Sanitize all user inputs before writing them in the logs. This includes checking its size, content, encoding, syntax, etc... As for any user input, validate using whitelists whenever possible. Enabling users to write what they want in your logs can have many impacts. It could for example use all your storage space or compromise your log indexing service.
      • Log enough information to monitor suspicious activities and evaluate the impact an attacker might have on your systems. Register events such as failed logins, successful logins, server side input validation failures, access denials and any important transaction.
      • Monitor the logs for any suspicious activity.



          Issue Links

          Java RSPEC-4839 Language-Specification Active Unassigned
          C# RSPEC-4889 Language-Specification Active Unassigned
          VB.NET RSPEC-4974 Language-Specification Active Unassigned
          PHP RSPEC-5092 Language-Specification Active Unassigned
          Python RSPEC-5226 Language-Specification Active Unassigned



              Unassigned Unassigned
              nicolas.harraudeau Nicolas Harraudeau (Inactive)
              0 Vote for this issue
              2 Start watching this issue