<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nehan Wijayagunarathna  on Medium]]></title>
        <description><![CDATA[Stories by Nehan Wijayagunarathna  on Medium]]></description>
        <link>https://medium.com/@nehanwijayagunarathna?source=rss-80a8a17ad2f6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qPmshzpsFMsA8S-8tRdiEA.jpeg</url>
            <title>Stories by Nehan Wijayagunarathna  on Medium</title>
            <link>https://medium.com/@nehanwijayagunarathna?source=rss-80a8a17ad2f6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:11:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nehanwijayagunarathna/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[48,000 CVEs and Counting: Why Understanding Vulnerabilities Has Never Been More Critical]]></title>
            <link>https://medium.com/@nehanwijayagunarathna/48-000-cves-and-counting-why-understanding-vulnerabilities-has-never-been-more-critical-1697a5306c2a?source=rss-80a8a17ad2f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/1697a5306c2a</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyber-awareness]]></category>
            <category><![CDATA[cve]]></category>
            <category><![CDATA[security-vulnerabilities]]></category>
            <dc:creator><![CDATA[Nehan Wijayagunarathna ]]></dc:creator>
            <pubDate>Fri, 16 Jan 2026 05:12:31 GMT</pubDate>
            <atom:updated>2026-01-16T05:21:51.057Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A little while ago, I was playing a Hack the Box machine, and I got stuck completely. Couldn’t move forward at all. Luckily, it was a retired machine, which means walkthroughs were available ( normally, if HTB machines are live, according to their policies, players can’t publish any walkthroughs ). So when I first looked it up, the noticeable thing I saw was: </em><strong><em>CVE-NNNN-NNNN.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aUSTgchK22vM3XqL" /><figcaption>Photo by <a href="https://unsplash.com/@lucabravo?utm_source=medium&amp;utm_medium=referral">Luca Bravo</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When I searched for that, I got a massive list of CVE entities. Why are there so many vulnerabilities (CVEs) out there?</p><h3>SO, What is a CVE ?</h3><p>Simply put, CVE stands for Common Vulnerability and Exposure. It&#39;s a standardized naming system maintained by MITRE Corporation. When someone, whether an individual researcher or an organization, discovers a security flaw, a general way to report it through the CVE system.</p><p>Think of it like this: CVE isn’t exploit code itself, it’s not malware, and it’s not a patch. It’s just a reference number, a unique identifier saying this specific vulnerability exists. These vulnerabilities can exist in software, hardware, or even firmware. The CVE system gives everyone a common language to talk about them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O9QEr0AKB7fSCEgMvtdjGA.png" /><figcaption>Photo on <a href="https://vulners.com/">vulners.com</a></figcaption></figure><h3>Why are there so many CVEs?</h3><p>Ok, here’s the thing. We live in a world filled with countless software applications, operating systems, hardware devices, and network configurations. Each of these has layers upon layers of code, components, and settings. While developing, they can make mistakes. Small errors slip through, and boom, vulnerabilities are born.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MbAMlsoHFDZ-3DVzmRZoRg.png" /><figcaption>Photo from <a href="https://www.cve.org/CVERecord/SearchResults?query=2025">cve.org</a></figcaption></figure><p>When CVEs are discovered, patches and updates are released to fix them. But here’s the catch: users don’t always update their products. Is there old software sitting on your computer? It might still have vulnerabilities that were patched years ago. Having a lot of CVEs doesn’t necessarily mean security is getting worse. In fact, it can mean the opposite: more vulnerabilities are being found and reported, which helps to fix those, but only if we use this information correctly.</p><h3>What Kinds of Things Get CVEs?</h3><p>Pretty much anything in the tech world can have vulnerabilities. We’re talking about software applications, web apps, operating systems, hardware, firmware, and even network configurations. If it runs code or handles data, it can potentially have a flaw that gets a CVE assigned to it. Let’s look at some real-world examples to make this clear:</p><p><strong>CVE-2025–55182 (React Vulnerability)</strong></p><p>CVE-2025–55182, named “React2shell”, is a critical remote code execution (RCE) vulnerability in React Server Components (RSC) and related packages. It was publicly disclosed on December 3, 2025, and carries the maximum severity score of 10.0 on the CVSS scale. In other words, it’s extremely dangerous and highly exploitable.</p><p><strong>CVE-2025–32463 (Sudo Vulnerability)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fvOeFEC7x_sWnbG-" /><figcaption>Photo by <a href="https://unsplash.com/@6heinz3r?utm_source=medium&amp;utm_medium=referral">Gabriel Heinzer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>CVE-2025–32463 is a critical local privilege escalation vulnerability affecting sudo versions 1.9.14 through 1.9.17. It allows an unprivileged local user to gain full root access on a system by abusing Sudo’s — chroot (-R) option. That’s the kind of vulnerability that keeps system administrators up at night.</p><p><strong>CVE-2025–7027 (UEFI Firmware Vulnerability)</strong></p><p>CVE-2025–7027 affects the Software System Management Interrupt (SMI) handler in UEFI firmware, particularly on certain Gigabyte motherboards. It stems from improper validation of pointers in the SwSmiInputValue 0xB2 handler. A local attacker with elevated privileges can manipulate read and write pointer values, leading to arbitrary memory writes in system Management RAM (SMRAM). This is a low-level, firmware-based attack vector.</p><p><strong>CVE-2024–43451 (Windows NTLMv2 Hash Disclosure)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5VmaUY3eO35FnUUG" /><figcaption>Photo by <a href="https://unsplash.com/@imsunnyhassan?utm_source=medium&amp;utm_medium=referral">Sunny Hassan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>CVE-2024–43451 is a spoofing vulnerability in Microsoft Windows that allows an attacker to trick a target system into disclosing the user’s NTLMv2 authentication hash. This can lead to credential theft and impersonation attacks, essentially, someone pretending to be you on a network.</p><h3>Let’s Get into the Real Thing</h3><p>When assessing a system&#39;s security, the first thing to check is the software component versions. Older versions without updates can create serious loopholes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tcSDAuSNIfjipSXuIi19Hw.jpeg" /><figcaption>version of the system is mentioned inside the source code</figcaption></figure><p>If you find an older version of any software, you might search for something like <em>“&lt;software name&gt; CVE vulnerabilities”. </em>And you will get something related cves. For example, when I search for the “<em>CrushFTP v=11.w.657 CVE vulnerability”, </em>I get CVE-2025–31161.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HRGlWZXPP3WbQQ2rAKtSzA.png" /></figure><p>But wait: what do those numbers actually mean? The “<em>2025</em>” indicates the year of vulnerability was reported. The “<em>31161</em>” is essentially a serial number. Each CVE can be uniquely identified by this year-serial number combination. That’s how the CVE catalogue stays organized.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*V4xwlK_Xl_CPS-WW3N_Z1g.png" /><figcaption>Photo from <a href="https://www.wallarm.com/what/common-vulnerabilities-and-exposures-cve">wallarm.com</a></figcaption></figure><h3>CVSS Scores</h3><p>When you dig into a CVE, you’ll encounter something called a CVSS score (Common Vulnerability Scoring System). Think of it as a severity rating from 0 to 10:</p><p><strong><em>None:0.0</em></strong></p><p><strong><em>Low:0.1–3.0</em></strong></p><p><strong><em>Medium:4.0–6.9</em></strong></p><p><strong><em>High:7.0–8.9</em></strong></p><p><strong><em>Critical:9.0–10.0</em></strong></p><p>In our case, CVE-2025–31161 scored a 9.8, which is a critical-level vulnerability. It needed to be patched immediately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/1*Eh5jWSYEvfT1RLJZSWBJ8A.jpeg" /></figure><h3>Vulnerability vs Exposure (Yes, There’s a Difference)</h3><p>Okay, let’s break this down because people often confuse these two terms.</p><blockquote>A <strong>vulnerability </strong>is a flaw, bug, or weakness in code, configuration, or process. For example, unpatched software or a weak password policy.</blockquote><blockquote>An <strong>Exposure </strong>is the condition that makes the flaw accessible to an attacker. For instance, if your vulnerable software is internet-facing or a particular port is left open.</blockquote><p>In other words, a vulnerability is the weakness itself; an exposure is what allows someone to actually exploit it.</p><h3>A Closer Look at CVE-2025–31161</h3><p>Let’s examine this vulnerability more closely. The flaw exists in the AWS4_HMAC authorization method of the HTTP component in CrushFTP’s server. A race condition in the <em>login_user_pass() </em>function allows authentication without password verification.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*byT1em67JZjQsKW5" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=medium&amp;utm_medium=referral">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The vulnerability can be established by sending a malformed AWS4-HMAC header containing only a username and a forward slash. This triggers successful authentication but fails to complete session cleanup due to an index-out-of-bounds error. The results? An attacker can authenticate as any known user, including the default administrator account “<em>crushadmin</em>”.</p><h3>Proof of Concept (PoC) — The Real Deal</h3><p>Now let’s talk about something called a <strong>Proof of Concept</strong>, or PoC for short. This is a real-world demonstration of how a CVE actually works in practice. It’s a way to verify that a particular vulnerability is feasible and exploitable just theoretical.</p><p>A PoC is typically code, a script, or a series of actions that, when combined with the right conditions, demonstrate how to gain access through the vulnerability. “<em>But isn’t that dangerous ?</em>” you might think. Actually, PoCs are incredibly useful:</p><ol><li><strong>Validate vulnerability</strong>: They provide concrete proof to developers and the security team that a reported flaw is real and exploitable, not just a theoretical concern.</li><li><strong>Facilitate communication</strong>: A working demonstration often explains complex security issues more effectively than a lengthy written report.</li><li><strong>Drive resolution</strong>: In research and development, PoCs prove the feasibility of new security measures and motivate faster fixes.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/777/1*ExXUut8TNvkbuPsE7NnU6w.jpeg" /></figure><p>PoCs are used across many areas: penetration testing, CTF competitions, academic research, and more. But here’s the critical point: the strength of a PoC lies in its ability to reveal weakness. Using PoC on systems you don’t own or don’t have explicit written permission to test is illegal and unethical.</p><p>Ethical hackers and security professionals always operate within the law (such as the Computer Fraud and Abuse Act in the US) and ensure all activities are authorised and documented. The goal of an ethical PoC is to improve security, not to cause damage or gain unauthorised access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xlt8s-U9BgFhdkzEFQ8SHg.jpeg" /><figcaption>The PoC file for CVE-2025–31161</figcaption></figure><h3>The Real-World Risk</h3><p>Let’s see how PoC works in the real world: While those resources are available on the internet, anyone can access them. Some websites rely on ftp services from platforms like <strong>CrushFTP, </strong>which can be risky. Without proper mitigation, websites can be hacked, data can leak, or various cyber attacks can become possible.</p><p>This is why there should be a clear process: find vulnerabilities, create PoC files to validate them, and develop mitigations to address those vulnerabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4FBR-yEPT2eU8EQBTtWSJQ.jpeg" /><figcaption>HTB platform environment</figcaption></figure><h3>Mitigations</h3><p>Since PoC files and related information are available online, security engineers work diligently to find solutions. This involves patching, updating systems, and releasing fixes for users to apply. Configuration changes, monitoring for security issues; it’s an ongoing process.</p><p>Why does this matter? because in this tech world, most critical systems depend on software, like hospitals, schools, and many more. Without proper mitigation, the consequences can be severe.</p><blockquote><strong>For CVE-2025–31161 specifically</strong>, CrushFTP has released patches to address the vulnerability. Users should immediately upgrade to version 10.8.4+ (for v10) or 11.3.1+ (for v11). If immediate patching isn’t possible, enabling the DMZ proxy instance of CrushFTP serves as a temporary mitigation, since the exploit doesn’t work with this configuration enabled.</blockquote><p>The vulnerability has been added to CISA’s Known Exploited Vulnerabilities Catalog with a remediation deadline of <strong>April 28, 2025</strong>.</p><h3>Who needs to Care About CVEs?</h3><p>CVEs are crucial not just in cybersecurity, but also in software development and the whole IT industry. Here’s who really needs to stay on top of these CVEs:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-RXG4xEh_-ag0lpD" /><figcaption>Photo by <a href="https://unsplash.com/@milan_malkomes?utm_source=medium&amp;utm_medium=referral">Milan Malkomes</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>SOC Teams</strong>: Security Operation Center teams are perhaps the most dependent on CVE updates. When new vulnerabilities are published, they need to update their monitoring system to be ready for potential attacks. CVE data helps prioritise responses and investigations, ensuring teams can act quickly to minimize risk.</p><p><strong>Vulnerability Scanners</strong>: Vulnerability scanners are used to test and find the weaknesses in systems. If these scanners aren’t updated with newly discovered CVEs, vulnerabilities can remain undetected, living inside systems without the awareness of developers or penetration testers. Attackers, however, might find and exploit these hidden flaws.</p><p><strong>Developers</strong>: If developers aren’t aware of security vulnerabilities, they might continue building on top of vulnerable systems. When these systems go live, the accumulated security debt can have serious consequences.</p><h3>At the End</h3><p>People across the IT industry need at least a basic understanding of CVEs and related concepts. With this knowledge, we can minimise attacks and reduce the risks. And as learners, we should use these tools responsibly, studying them to improve security, not to cause harm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3Nz5YuQ8Bb4_WEZz" /><figcaption>Photo by <a href="https://unsplash.com/@flyd2069?utm_source=medium&amp;utm_medium=referral">FlyD</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><a href="https://blog.rotaractmora.org/48-000-cves-and-counting/"><em>This article was also published on the Rotaract Mora blog</em></a></p><h3>Reference</h3><p>Here are some resources that I used to craft this article.</p><p><a href="https://www.hackthebox.com/machines/soulmate">Join The Best Hacking Community Worldwide | Hack The Box</a></p><p><a href="https://moxso.com/blog/glossary/proof-of-concept-poc"><em>moxso.com/blog/glossary/proof-of-concept-poc</em></a></p><p><a href="https://www.wiz.io/vulnerability-database"><em>wiz.io/vulnerability-database</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1697a5306c2a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are DevOps processes secure in nature?]]></title>
            <link>https://medium.com/@nehanwijayagunarathna/are-devops-processes-secure-in-nature-d73179e1cdca?source=rss-80a8a17ad2f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/d73179e1cdca</guid>
            <category><![CDATA[devops-security]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[devops-tool]]></category>
            <dc:creator><![CDATA[Nehan Wijayagunarathna ]]></dc:creator>
            <pubDate>Sun, 26 Oct 2025 15:32:58 GMT</pubDate>
            <atom:updated>2025-10-26T16:54:44.567Z</atom:updated>
            <content:encoded><![CDATA[<p>DevOps is essential for delivering software quickly and reliably. By integrating development and operations, DevOps streamlines the software development lifecycle from coding and building to testing and deployment, enabling faster delivery and improved collaboration. However, speed and automation do not guarantee security. Security needs to be intentionally integrated into every stage of the DevOps pipeline to protect applications and infrastructure from evolving threats.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N8Qszjx4EEEtwzYjzZVmxA.png" /><figcaption>Photo on <a href="https://www.atlassian.com/devops">atlassian.com</a></figcaption></figure><h3><strong>What is DevOps?</strong></h3><p>DevOps is a convergence of cultural philosophies, emerging tools, and practices that aim to automate and simplify the entire software development lifecycle. This strategy spans everything from original code development to ultimate deployment.</p><p>The process evolves through discrete steps:</p><p><strong>1.Build Stage</strong></p><p>Developers build the codebase and use automation tools (e.g., GitHub Actions, Jenkins, GitLab CI/CD). External libraries and package managers (Gradle, Maven, npm) speed development but introduce supply-chain risk if dependencies are outdated or malicious .</p><p><strong>2.Test Stage</strong></p><p>Code is extensively tested for bugs and security issues with various methodologies like unit testing, integration testing, performance testing, and security audits. Popular tools among them include <em>Selenium, JUnit, TestNG, and SonarQube</em>.</p><p><strong>3.Release Stage</strong></p><p>Pre-deployment testing replicates real-world scenarios. Different plans of deployment ensure transitions are smooth:</p><blockquote>Blue-Green Deployment <strong>:</strong> Two different environments ensure that traffic shifting is smooth when updating</blockquote><blockquote>Canary Deployment : A subset of users receives the new version initially for security checks</blockquote><blockquote>Rolling Updates : Gradual rollout encompasses all users progressively</blockquote><p>Major tools are <em>Docker, Kubernetes, Ansible, Helm, and ArgoCD</em>.</p><p>In cases where newly deployed versions introduce bugs or vulnerabilities, rollback mechanisms are crucial for restoring previous stable states quickly. Rollback allows teams to revert to an earlier version of the application or configuration without major downtime, maintaining reliability and user trust. Automated rollback strategies can be built into CI/CD pipelines, ensuring that failed deployments trigger instant recovery. This not only minimizes disruption but also strengthens the resilience of DevOps environments.</p><p>Under the DevOps model, there are multiple teams coordinating along this lifecycle, typically Quality Assurance and Security teams. They collaborate to automate the development and deployment processes for maximum efficiency and reliability.</p><h3><strong>Why is DevOps?</strong></h3><p>The Internet and Software technologies drive the current technology revolution. Companies in industries like healthcare, education, and others require frequent updates of technology. Organizations require faster development, consistency of systems, reliability, and security to compete. DevOps delivers these requirements effectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8e0zW8MVHM_ezP523Bc26Q.png" /><figcaption>Photo on <a href="https://thectoclub.com/devops/devops-team/">thectoclub.com</a></figcaption></figure><p><strong>1.Speed Enhancement</strong></p><p>DevOps accelerates operations by eliminating human processes, encouraging frequent code changes, automated testing procedures, and increased collaboration among teams.</p><p><strong>2.Rapid Delivery Speed</strong></p><p>Automated deployment and continuous delivery tools allow for small, frequent, and secure releases. This allows for faster bug fixes and quicker responses to customer requirements.</p><p><strong>3.Reliability Assurance</strong></p><p>DevOps ensures quality by validating application and infrastructure changes. Continuous Integration &amp; Delivery (CI/CD) auto-validates with testing, so that each change is working and secure, enabling proactive error fixing.</p><p><strong>4.Scalability Support</strong></p><p>DevOps handles complicated systems well, keeps errors low with automation, views infrastructure as code, and maintains risk low through repeatable and reliable processes.</p><p><strong>5.Improved Collaboration</strong></p><p>DevOps builds better, more efficient teams based on ownership and accountability models. Developers and operations teams collaborate closely, share workloads, and integrate workflows for best results.</p><h3><strong>Key DevOps Practices</strong></h3><p>DevOps practices refer to techniques, guidelines, principles, and tools used in managing software development and deployment. The main objective is to enhance delivery speed and system reliability through automation, monitoring, and collaboration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6kuTA01wuVgATUp-Y8hgcg.png" /><figcaption>Photo on <a href="https://opsera.ai/blog/all-you-need-to-know-about-ci-cd-pipeline/">opsera.ai</a></figcaption></figure><p><strong>1.Continuous Integration (CI)</strong></p><p>Developers will typically commit changes to shared repositories. Even minor changes trigger automated tests to run in hopes of catching bugs early.</p><p><strong>2.Continuous Delivery (CD)</strong></p><p>Continuous Delivery is utilized for automating the release pipeline so that builds are continually tested and deployment-ready.</p><p><strong>3.Continuous Deployment</strong></p><p>Continuous Deployment goes a step further from the above practice by deploying every approved change automatically into production environments.</p><p><strong>4.Infrastructure as Code (IaC)</strong></p><p>A DevOps practice that uses machine-readable definition files to manage and provision data center resources like networks, servers, and storage, rather than relying on manual configurations or physical hardware.</p><p><strong>5.Configuration Management</strong></p><p>Systematic tracking and management of changes to system components, their attributes, and relationships throughout their entire lifecycle.</p><p><strong>6.Automated Testing</strong></p><p>Executes testing processes in order to deliver high-quality code as well as early detection of issues within the development cycles.</p><p><strong>7.Monitoring and Logging</strong></p><p>Monitors real-world behavior and identifies problems before they strike.</p><p><strong>8.Incident Response and Alerting</strong></p><p>Monitoring discovers all types of problems requiring immediate alerting and rapid response to minimize damage.</p><p><strong>9.Containerization</strong></p><p>Packages up applications in extremely light, transportable containers (like Docker) to deliver consistency across all environments.</p><p><strong>10.Environment Automation</strong></p><p>Automates uniform development, testing, staging, and production environments to avoid mistakes and maximize efficiency.</p><h3><strong>Common Vulnerabilities</strong></h3><h4><strong>1. Misconfiguration Vulnerabilities</strong></h4><blockquote>Misconfiguration is one of the largest DevOps weaknesses, caused by setup, permissions handling, or automation. The speed and depth of these processes may result in such errors. Correct configuration is still of the highest importance; otherwise, attackers may gain administrative privileges and view sensitive data.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*m1nFvMHrZKhjBvKkudGM4w.jpeg" /><figcaption>Photo on <a href="https://www.wallarm.com/what/security-misconfiguration">wallarm.com</a></figcaption></figure><p><strong>IaC Vulnerabilities</strong></p><p>IaC tools like Terraform, CloudFormation, and Ansible allow developers to provision and define infrastructure through code. Misconfigurations tend to propagate security weaknesses to whole environments at a rapid pace.</p><ul><li>Overly permissive access controls that set IAM policies with too broad permissions, potentially enabling privilege escalation</li><li>Exposed storage buckets as a result of misconfigured cloud storage (e.g., AWS S3 buckets) becoming public</li><li>Manual drift through changes made manually, causing the deployed infrastructure to diverge from IaC templates and create security blind spots</li></ul><p><strong>CI/CD Pipeline Vulnerabilities</strong></p><p>The scripted nature of Continuous Integration/Continuous Deployment pipelines can cause misconfigurations to spread quickly from development to production.</p><ul><li>Overly permissive pipeline permissions give CI/CD processes overly broad access, which attackers can use for lateral movement</li><li>Outdated dependencies using software or open-source libraries with known vulnerabilities</li><li>Integrity checks are missing that allow unverified code changes or dependencies to be added without proper verification.</li></ul><p><strong>Cloud Services Misconfigurations</strong></p><p>Cloud platform complexity, with so many features and configurations, tends to lead to production environment misconfigurations.</p><p>Invariant default configurations, such as default admin credentials left enabled, network exposure with public internet access on non-essential ports. Inadequate logging and monitoring make incident detection and response harder. Development settings in production environments leak sensitive information through verbose error messages.</p><h4><strong>2. Vulnerable Containers</strong></h4><p>Containerization is at the heart of modern DevOps. From base image creation to container deployment, some disturbing practices can emerge.</p><ul><li><strong>Vulnerable Base Images</strong></li></ul><p>Insecure base images are vulnerable base container layers containing known vulnerabilities, malware, or misconfigurations that a hacker could exploit. Due to the layered construction of container images, any security vulnerabilities found in base images are propagated to all derived containers.</p><ul><li><strong>Unpatched Software</strong></li></ul><p>Software patches usually provide security patches safeguarding against attack vectors. Failing to apply them results in vulnerable software reaching production environments.</p><ul><li><strong>Privilege Policies</strong></li></ul><p>Containers must run under least privilege policies to restrict access. When containers are run with root privileges without certain restrictions, it makes it easier for attackers. Containers need to be given only the privileges needed for their specific use, as too much privilege can leak sensitive information or introduce attack surfaces.</p><h4><strong>3. Secrets Management Vulnerabilities</strong></h4><p>Secret management vulnerabilities typically occur through a lack of supervision, insecure infrastructure, or human error in software build and deployment processes. These issues are particularly prevalent in high-stress DevOps environments where security is deprioritized for velocity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ejFfi2HtBvg7D94RDkTZw.png" /><figcaption>Photo on <a href="https://cpl.thalesgroup.com/blog/access-management/enterprise-secrets-management-explained">thalesgroup.com</a></figcaption></figure><ul><li><strong>Decentralized Secret Management</strong></li></ul><p>Without dedicated, centralized systems or “vaults” for storing secrets, organizations create disorganized environments that can be exploited.</p><ul><li><strong>Hardcoded Secrets</strong></li></ul><p>Hardcoding of sensitive credentials into source code, scripts, or config files is a proven and highly risky mistake.</p><ul><li><strong>Secret Leakage</strong></li></ul><p>Accidental leakage of secrets through code, logs, or network traffic can lead to unauthorized access, data breaches, and economic impact.</p><h4><strong>4. Lack of Shared Ownership</strong></h4><p>While DevOps culture is teamwork-oriented, having so many people involved can create shared ownership dangers. This creates responsibility ambiguity and system security vulnerabilities that are difficult to fix and costly to companies.</p><ul><li><strong>Blame Assignment</strong></li></ul><p>Without shared responsibility, teams will create suboptimal solutions where blame is placed on failure. The “us versus them” mindset between departments erodes security objectives.</p><ul><li><strong>Security as an Afterthought</strong></li></ul><p>If security is viewed as a task only for the security team, then it becomes an end-of-process checkpoint rather than being integrated into the development process. End-of-process security testing is time-consuming and expensive, and vital issues might be missed.</p><h4><strong>5. Over-Automation and Lack of Oversight</strong></h4><p>Over-automation and poor monitoring in DevOps create security vulnerabilities through interconnected technical and cultural aspects. Urgency to move fast often outweighs security needs, causing teams to automate without proper guardrails, training, or feedback. This sets up systems where defects transmit rapidly and attackers can easily find and exploit vulnerabilities.</p><h4><strong>6. Automating critical security processes</strong></h4><p>Teams may automate existing, broken, or inefficient manual workflows without fixing the underlying issues first. This doesn’t eliminate the problems it just makes them happen faster, at scale.</p><h4><strong>7. Unchecked Deployments</strong></h4><p>CI/CD pipelines that are too dependent on automation could be deploying code to production too quickly and skipping or avoiding security checks to meet aggressive timelines, arguably increasing the risk of deploying insecure code.</p><h4><strong>8. Bypass critical reviews</strong></h4><p>Lacking proper code reviews, quality gates, and constant monitoring, bad code can ship stealthily. The lack of visibility allows bugs and flaws to reside in production.</p><h4><strong>9. Poor Access Controls</strong></h4><p>Granting excessive privileges to users or tools increases the risk of widespread damage if compromised. Misalignment between development and security teams leads to security being deprioritized in favor of speed.</p><p>DevOps is more effective, but is a security risk if not controlled. It has vulnerabilities like cloud and infrastructure-as-code (IaC) configuration misconfigurations that reveal sensitive data. CI/CD pipelines typically face bad permissions, out-of-date libraries, and missing integrity checks. Container security risks are due to insecure base images and unpulled software, and poor secrets management (e.g., hardcoded passwords and secret exposure) is also under attack. Absence of collective responsibility for security and over-automation also bypasses key security checks and leads to unchecked deployments. These loopholes provide access for the attackers to take advantage of vulnerabilities and gain unauthorized access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KDUPWnNlsLP9VM-0_oIL3Q.png" /><figcaption>Photo on <a href="https://www.atlassian.com/devops/devops-tools/devsecops-tools">atlassian.com</a></figcaption></figure><p><strong>How do attackers take advantage of these loopholes to gain access, and how can they be avoided?</strong></p><p><a href="https://blog.rotaractmora.org/are-devops-processes-secure-in-nature/"><em>This article was also published on the Rotaract Mora blog</em></a></p><h3>References</h3><p>Here are some resources that I used to craft this article.</p><ol><li><a href="https://aws.amazon.com/devops/what-is-devops/">aws.amazon.com/devops/</a></li><li><a href="https://www.atlassian.com/devops/">atlassian.com/devops</a>/</li><li><a href="https://www.geeksforgeeks.org/devops/introduction-to-devops/">geeksforgeeks.org/devops</a>/</li><li><a href="https://owasp.org/www-project-devsecops-guideline/">owasp.org/www-project-devsecops-guideline/</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d73179e1cdca" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>