The nail group monitors the CVE information of Github

Posted by twsowerby on Wed, 09 Feb 2022 22:09:55 +0100

Monitor CVE-2022 related information in Github through nail group to realize robot message push.

1, Database information

Create the mysql database cvemonitor and import the sql file into the database. The sql statement is as follows:

SET NAMES utf8mb4;

-- ----------------------------

-- Table structure for github_monitor

-- ----------------------------

DROP TABLE IF EXISTS `github_monitor`;
CREATE TABLE `github_monitor`  (
  `cve_name` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `cve_url` varchar(100) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL,
  `cve_description` mediumtext CHARACTER SET utf8 COLLATE utf8_general_ci,
  UNIQUE INDEX `cve_name`(`cve_name`) USING BTREE


2, Monitoring script

Note: the script needs execution permission chmod 777

import requests
import json
import dingtalkchatbot.chatbot as cb
import time
import pymysql

# Connect database
conn = pymysql.connect(host="Database host IP", user="Database account name", password="Database password", database="Database name",charset="utf8")
# Set the webhook value and secukey value of the nail group robot
webhook = 'Fill in the user-defined robot of nailing intelligent group assistant here webhook'
sckey = 'Fill in the key of nail smart group assistant custom robot here'

def dingding(text, msg,webhook,secretKey):
    ding = cb.DingtalkChatbot(webhook, secret=secretKey)
    ding.send_text(msg='{}\r\n{}'.format(text, msg), is_at_all=False)

def check(cve_name,url,cve_description):
        # Get a cursor object that can execute SQL statements
        cursor = conn.cursor()
        sql = '''insert into github_monitor(cve_name,cve_url,cve_description) values('{}','{}','{}')'''.format(cve_name,url,cve_description)
        print("Database inserted successfully")
        # Execute SQL statement
        body = "CVE No.:" + cve_name + "\r\n" + "Github Address:" + url + "\r\n" +"Description:"+ cve_description + "\r\n"
        dingding('There are new ones CVE find', body, webhook, sckey)
        print("Nail sending CVE success")
    except Exception as e:
        print('Should CVE{}Already exists'.format(cve_name))
    except Exception as e:

if __name__ == '__main__':
    while True:
        now_time=time.strftime("%Y-%m-%d %H:%M:%S", time.localtime())
        print('*     The current detection time is:'+now_time+'      *')
        github_headers = {
            'Authorization': 'token {}'.format('Fill in here github of token') 
        url = ''
            result = requests.get(url=url, headers=github_headers).text
            result = json.loads(result)
            for i in range(1, 20):
                url = result['items'][i]['html_url']
                cve_name = result['items'][i]['name']
                cve_description = result['items'][i]['description']
                check(cve_name, url,cve_description)
        except Exception as e:
        time.sleep(30*60) #Every 30 minutes, the number of seconds to delay execution

3, Configure the shell script ( to execute the monitor

The script detects whether the server has a process to monitor the script. If there is no process, execute the command to start the script in the background

Note: the script needs execution permission chmod 777

export PATH=usr/lib/jvm/java-1.8.0-openjdk-

ps aux |grep "python3 -u /opt/cvemonitor/" |grep -qv "grep"
if [ $? -ne 0 ];then
    rm -rf out.log
    nohup python3 -u /opt/cvemonitor/ >/opt/cvemonitor/out.log 2>&1 &
    echo "start-up cve Monitoring script succeeded"
    echo "cve Monitoring script is running"

4, Configure scheduled tasks

1. CVE scheduled start task_ run. SH script

vi /etc/crontab

# For details see man 4 crontabs

# Example of job definition:
# .---------------- minute (0 - 59)
# |  .------------- hour (0 - 23)
# |  |  .---------- day of month (1 - 31)
# |  |  |  .------- month (1 - 12) OR jan,feb,mar,apr ...
# |  |  |  |  .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
# |  |  |  |  |
# *  *  *  *  * user-name  command to be executed
# Time sharing day month week 
# Execute the script every minute

* * * * *  /opt/cvemonitor/

2. Save scheduled tasks and view scheduled task execution logs

crontab /etc/crontab   #Save and load the scheduled task to make it effective
service crond restart   #Restart the scheduled service and take effect immediately
# View scheduled tasks
crontab -l
# Use the command to view the execution log of crontab: / var/log/cron will only record whether some scheduled scripts have been executed
tail -f /var/log/cron

5, Nail group assistant and Github

1. Creating nail intelligent group assistant robot

Add robot:

Select a custom robot:

Copy the key and Webhook into the python script:

2. Github Token value

Enter the configuration of personal account and select Developer settings:

Copy the Token value in the figure above to the python script.

6, Start monitoring script and precautions

1. Startup script

Use nohup to start the monitoring script CVE monitor in the background Py and save the output to out log

nohup python3 -u /opt/cvemonitor/ >/opt/cvemonitor/out.log 2>&1 &
  1. The last "&" indicates the background running program

  2. "nohup" means that the program is not suspended

  3. "Python3" means to execute Python code using python3

  4. "- U" means that the cache is not enabled and the print information is output to the log file in real time (if - u is not added, the log file will not refresh the information of the print function in the code in real time)

  5. "" indicates the source code file of python

  6. "test.log" indicates the output log file

  7. ">" indicates that the print information is redirected to the log file

  8. "2 > & 1" means that the standard error output is changed to standard output, and the error information can also be output to the log file (0 - > stdin, 1 - > stdout, 2 - > stderr)

2. Restart the scheduled task to ensure that the scheduled task takes effect

service crond restart

3. Problems encountered

After the scheduled task is configured and started, I can see that the scheduled task executes CVE normally by checking the log cat /var/log/cron_ run. SH script but CVE monitor Py script did not start normally.

Come to CVE_ run. The directory of the SH script. Use the command sh executes the shell script, and then checks the process. It is found that the python script process executes normally; So why can't you start a python monitor program with a shell script through a scheduled task? It turned out to be the problem of environmental variables

Use the env |grep PATH command to view the environment variables of the current server, copy the contents of the paragraph PATH = and add it to the scheduled task script in #/ The following line of bin/bash specifies the environment variables

export PATH= 

6, Summary

Monitor CVE-2022 related information in Github through nail group to realize robot message push.

Main ideas:

  1. Command background startup script
  2. The scheduled task executes the shell script to detect whether the monitoring program is running. If the program fails, re execute the start command

Topics: github cve