Dilan Nonis’ Post

New blog post! This is part 2d in continuation of the authorization series. In this part I have discussed about by-passing HTTP method based access control due to platform misconfiguration. Further there is a step-by-step solution for the Web Security Academy lab "Lab: Method-based access control can be circumvented". https://lnkd.in/gmAF6hfK #Portswigger #WebSecurityAcademy #CyberSecurity #InfoSec #WebSecurity #MediumBlogging

Intelmq leverages Shadowserver’s APIs. This is a way to check out the APIs. https://lnkd.in/gt4Q9ckx The APIs open synergistic opportunities. You can use the APIs to intergrate Shadowserver’s data with your other telemetry and risk indicators.

Discover how CVE-2024-29510, a critical Ghostscript vulnerability, could be the gateway to RCE and significant breaches even with sandbox protections compromised. Stay informed and secure! #cybersecurity #security #news https://lnkd.in/e8URmz5Y

It's #fortra patch time "Fortra Releases Update on Critical Severity RCE Flaw" The flaw has a CVSS rating of 9.8, and the company recommends product upgrades to fix the issue. This part of the article make me think that something is not right with the internal security culture : "Though Fortra has been aware of the bug since it was initially reported months ago, it is issuing a CVE now at the request of the individual who reported the vulnerability in the first place." I mean, really ? connected=hacked #cybersecurity FAIL https://lnkd.in/e3wk3PGD

Strong smart contract security is pivotal in safeguarding your Web3 project against vulnerabilities and ensuring trustworthiness. Here's what to look out for when creating a contract: Comprehensive Audits: Always get your smart contracts audited by reputable firms. This highlights vulnerabilities and reassures users about your project's security. Open Source Libraries: Use well-tested and widely accepted libraries to reduce the risk of bugs in your code. Limit Functions: To minimize potential attack surfaces, keep your contracts simple with clearly defined functions. Upgradable Contracts: Design contracts with future updates in mind, allowing for adjustments as security practices evolve. Platforms like Blubird, with our audited Deployment Module, can significantly ease this process by providing an in-depth framework for launching secure and efficient smart contracts, ensuring your project's integrity from the start.

This is cool. Many if not most of my connections do not work for Fortune 2000 companies with a dedicated SOC and SIEM. Cybersecurity and Infrastructure Security Agency just published a fantastic freebie made just for you: "Logging Made Easy." It's a collection of docs and installation guides to set up sysmon for log generation; WEC to ship logs; and an Elastic stack to store and query the logs. It even has some built-in Kibana dashboards to get you started with making sense of the logs. https://lnkd.in/gwd5b4Hv

I just learnt the fundamentals of API Security from APIsec University.

🚨 Attention Developers and AppSec pros! Did you hear about what’s happening with the NVD? 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐠𝐨𝐢𝐧𝐠 𝐨𝐧? The NVD is experiencing delays in fully analyzing and tagging reported vulnerabilities since mid-February and it manifested in: --> Fully tagging CVEs: This means critical information like the affected software components (CPE) and the vulnerability's severity (CVSS) might be missing. --> Addressing the backlog: Thousands of 2024 CVEs remain untagged, hindering the ability of some vulnerability management solutions to function effectively. 𝐖𝐡𝐲 𝐢𝐬 𝐭𝐡𝐢𝐬 𝐢𝐦𝐩𝐨𝐫𝐭𝐚𝐧𝐭? Many vulnerability scanners rely solely on the NVD for data. Without proper tagging, these solutions may: --> Miss critical vulnerabilities: They might not identify all security risks your software faces due to the lack of CPE information. --> Cause false negatives: You might be lulled into a false sense of security if vulnerabilities affecting your specific software go unreported. 𝐖𝐡𝐚𝐭 𝐚𝐛𝐨𝐮𝐭 𝐌𝐞𝐧𝐝.𝐢𝐨? Mend.io is not affected by this NVD issue.  We source our vulnerability data from multiple reliable sources and have taken steps to ensure comprehensive coverage, including the information currently lacking in the NVD. Mend SCA customers can rest assured. Our solution continues to accurately identify and report vulnerabilities within your software. Mend Renovate users are also protected. By keeping your dependencies up-to-date, you're effectively mitigating almost all CVEs. Read our latest blog post offering more details and recommendation. https://lnkd.in/ds3YwJpy #nvd #cve #vulnerabilitymanagement #applicationsecurity #appsec

🚨 Attention Developers and AppSec pros! Did you hear about what’s happening with the NVD? 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐠𝐨𝐢𝐧𝐠 𝐨𝐧? The NVD is experiencing delays in fully analyzing and tagging reported vulnerabilities since mid-February and it manifested in: --> Fully tagging CVEs: This means critical information like the affected software components (CPE) and the vulnerability's severity (CVSS) might be missing. --> Addressing the backlog: Thousands of 2024 CVEs remain untagged, hindering the ability of some vulnerability management solutions to function effectively. 𝐖𝐡𝐲 𝐢𝐬 𝐭𝐡𝐢𝐬 𝐢𝐦𝐩𝐨𝐫𝐭𝐚𝐧𝐭? Many vulnerability scanners rely solely on the NVD for data. Without proper tagging, these solutions may: --> Miss critical vulnerabilities: They might not identify all security risks your software faces due to the lack of CPE information. --> Cause false negatives: You might be lulled into a false sense of security if vulnerabilities affecting your specific software go unreported. 𝐖𝐡𝐚𝐭 𝐚𝐛𝐨𝐮𝐭 𝐌𝐞𝐧𝐝.𝐢𝐨? Mend.io is not affected by this NVD issue.  We source our vulnerability data from multiple reliable sources and have taken steps to ensure comprehensive coverage, including the information currently lacking in the NVD. Mend SCA customers can rest assured. Our solution continues to accurately identify and report vulnerabilities within your software. Mend Renovate users are also protected. By keeping your dependencies up-to-date, you're effectively mitigating almost all CVEs. Read our latest blog post offering more details and recommendation. https://lnkd.in/ds3YwJpy #nvd #cve #vulnerabilitymanagement #applicationsecurity #appsec

The "kubeaudit all" command is part of the kubeaudit tool, which is used for auditing Kubernetes clusters for security vulnerabilities and best practices. When you run "kubeaudit all", it performs a comprehensive audit of various Kubernetes resources in your cluster, including pods, deployments, services, and more, to identify potential security issues. Here's how the "kubeaudit all" command works and an example of its usage: Function: "kubeaudit all" performs a thorough audit of all Kubernetes resources in the cluster, checking for security risks and compliance with best practices. It analyzes various aspects of the resources, such as container configurations, pod security contexts, service configurations, and network policies. The command provides detailed feedback on any findings, including recommendations for remediation and links to relevant documentation. It's important to note that you may need appropriate permissions to access and audit resources in the Kubernetes cluster. Additionally, kubeaudit should be installed and configured correctly in your environment before running the "kubeaudit all" command. Example of what you may see when you execute the command:- Error: Pod has insecure `runAsUser` configuration Severity: Critical Recommendation: Update the pod's security context to use a non-root user. Affected Resource: Pod nginx-deployment-1 Warning: Kubernetes secret is not encrypted at rest Severity: Moderate Recommendation: Enable encryption at rest for Kubernetes secrets. Affected Resource: Secret my-secret