Vulnerability Details

Linux: Get crontab and /etc/cron.* scripts

Published: 2020-11-26 14:08:34

CVSS Base Vector:
AV:L/AC:H/Au:S/C:N/I:N/A:N

Report Confidence:
97

Summary:
Crontab is the program used to install, remove or list the tables used to drive the cron(8) daemon. Each user can have their own crontab, and though these are files in /var/spool/, they are not intended to be edited directly. For SELinux in mls mode can be even more crontabs - for each range. Many of the services use crontab automatically. They store their crontab scheduler configuration directly into /etc/cron.d directory. Any files located in this directory are automatically picked up and executed by the crontab scheduler. Linux system administrators can also take an advantage of crontab preconfigured schedules directories /etc/cron.daily, /etc/cron.hourly, /etc/cron.monthly and /etc/cron.weekly. The crontab files located within these directories are periodically traversed and execute by crontab scheduler. So for example crontab files found in /etc/cron.daily directory are executed every day. Furthermore, if root wishes to run eg. backup.sh script once a week he will place it into /etc/cron.weekly directory. Note: This script gets the crontab for root user and content of files /etc/cron.*

References:

https://linux.die.net/man/1/crontab
https://linuxconfig.org/linux-crontab-reference-guide

Severity
Detection Plugin
CVSS Score
0.0
Published
2020-11-26
Modified
2020-12-16
Category
Policy

Free Vulnerability Scanning, Assessment and Management

Mageni's Platform is packed with all the features you need to scan, assess and manage vulnerabilities like this - it is free, open source, lightning fast, reliable and scalable.

Router
Servers
Laptop
Database
Group
Cloud

Frequently Asked Questions

No, you can scan concurrently as many assets as you want. Please note that you must be aware of the hardware requeriments of the platform to ensure a good performance.

No, you can add as many assest as you want. It doesn't matters if you have millions of assets, we won't charge you for that.

No. The software is completely free. We have no intention to charge you to use the software, in fact - it completely goes against our beliefs and business model.

A vulnerability is defined in the ISO 27002 standard as “A weakness of an asset or group of assets that can be exploited by one or more threats” (International Organization for Standardization, 2005)

We generate revenue by providing support and other services for customers that require a subscription so they get guaranteed support and enterprise services. To use Mageni's Platform is completely free, with no limits at all.

Yes. Mageni understands that there are professionals and businesses that need commercial support so Mageni provides an active support subscription with everything needed to run Mageni's Platform reliably and securely. More than software, it's access to security experts, knowledge resources, security updates, and support tools you can't get anywhere else. The subscription includes:

  • Ongoing delivery
    • Patches
    • Bug fixes
    • Updates
    • Upgrades
  • Technical support
    • 24/7 availability
    • Unlimited Incidents
    • Specialty-based routing
    • Multi-Channel
  • Commitments
    • Software certifications
    • Software assurance
    • SLA

No, we don't store the information of your vulnerabilities in our servers.

Vulnerability management is the process in which vulnerabilities in IT are identified and the risks of these vulnerabilities are evaluated. This evaluation leads to correcting the vulnerabilities and removing the risk or a formal risk acceptance by the management of an organization. The term vulnerability management is often confused with vulnerability scanning. Despite the fact both are related, there is an important difference between the two. Vulnerability scanning consists of using a computer program to identify vulnerabilities in networks, computer infrastructure or applications. Vulnerability management is the process surrounding vulnerability scanning, also taking into account other aspects such as risk acceptance, remediation etc. Source: "Implementing a Vulnerability Management Process". SANS Institute.

I am ready to start scanning for vulnerabilities