Skip to main content

Exim bug CVE-2019-10149 fixes

If you have cpanel license and can update it to the latest non-vulnerable patched version, then it is the easiest fix , else please do the below steps:



Complete below modification and restart exim, also check mail service by sending test mail. Also make sure to take backup of exim.conf, before modification

Open /etc/exim.conf, SEARCH FOR acl_not_smtp:* and add below content


###############################
deny
    condition = ${if lt {$exim_version}{4.92}{1}{0}}
    condition = ${if forany{<,$recipients}{match_local_part{$item}{\N^.*\$\{.*$\N}}{yes}{no}}
    message = restricted characters in recipient address

deny
    condition = ${if lt {$exim_version}{4.92}{1}{0}}
    condition = ${if match{$sender_address_local_part}{\N^.*\$\{.*$\N}{yes}{no}}
    message = restricted characters in sender address

# END INSERT 000_restricted_chars
# BEGIN INSERT resolve_vhost_owner
warn
        condition   = ${if eq{$originator_uid}{${perl{user2uid}{nobody}}}{1}{0}}
        set acl_c_vhost_owner = ${perl{resolve_vhost_owner}}
##############################


Search for acl_smtp_rcpt: and add below content*

############################
deny
    condition = ${if lt {$exim_version}{4.92}{1}{0}}
    local_parts = \N^.*\$\{.*$\N
    message = restricted characters in recipient address

deny
    condition = ${if lt {$exim_version}{4.92}{1}{0}}
    senders = \N^.*\$\{.*$\N
    message = restricted characters in sender address
###########################

After that please do the below steps :
######################################

1:  Remove /etc/ld.so.preload

rm -f /etc/ld.so.preload
rm -f  /lib/libgrubd.so

2: check .ssh/authorized_keys file, if anything unusual entries in authorized_keys please clear all except ezeelogin server key and set attribute for .ssh/authorized_keys

Comments

Post a Comment

Popular posts from this blog

K8s External Secrets integration between AWS EKS and Secrets Manager(SM) using IAM Role.

What is K8s External Secrets and how it will make your life easier? Before saying about External Secrets we will say about k8s secrets and how it will work. In k8s secrets we will create key value pairs of the secrets and set this as either pod env variables or mount them as volumes to pods. For more details about k8s secrets you can check my blog http://jinojoseph.blogspot.com/2020/08/k8s-secrets-explained.html   So in this case if developers wants to change the ENV variables , then we have to edit the k8s manifest yaml file, then we have to apply the new files to the deployment. This is a tiresome process and also chances of applying to the wrong context is high if you have multiple k8s clusters for dev / stage and Prod deployments. So in-order to make this easy , we can add all the secrets that is needed in the deployment, in the AWS Secret Manager and with the help of External secrets we can fetch and create those secrets in the k8s cluster. So what is K8s external Secret? It i...
Post a Comment
Read more

Password reset too simplistic/systematic issue

Some time when we try to reset the password of our user in linux it will show as simple and systematic as below: BAD PASSWORD: it is too simplistic/systematic no matter how hard password you give it will show the same. Solution: ######### Check if your password is Ok with the below command, jino@ndz~$ echo 'D7y8HK#56r89lj&8*&^%&^%#56rlKJ!789l' | cracklib-check D7y8HK#56r89lj&8*&^%&^%#56rlKJ!789l: it is too simplistic/systematic Now Create a password with the below command : jino@ndz~$ echo $(tr -dc '[:graph:]' 7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K; You can see that this password will be ok with the cracklib-check. jino@ndz~$ echo '7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K;' | cracklib-check                 7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K;: OK Thats all, Thanks.
Post a Comment
Read more

LXC Containers and How it differs from VMs and Docker Containers?

VM vs LXC ########## The main difference between the VMs and Containers is that virtual machines require their own kernel instance to run while  containers  share the same kernel. In other words,  containers  are virtualization at operating-system-level whereas  VMs  are virtualization at the hardware level. In virtual Machines each Guest OS will have its own Operating System and kernel. But in the case of LXC Containers the Guest OS will share the same OS of its Host machine. LXC vs Docker ############# LXC is a container technology that gives us the lightweight Linux containers and Docker is single application virtualisation which is based on top of the containerd Run time engine.. Thus even though based on container utilisation they may sound similar but they are completely different when it comes to usage. Unlike the lightweight LXC containers, docker does not tend to behave lightweight VM’s. Single application restriction of the docker is strictly by t...
Post a Comment
Read more