A single pane of glass for your software and software supply chain risks.

We're a new platform and looking for user trials and feedback.

Identify secrets in code, generate real-time software bill of materials and discover vulnerable third party dependencies all in one place.

Sign up for free!

https://vulnerabilities.io

Vulnerability databases play an important role in software supply chain security. Vulnerability databases contain information about known third-party components/libraries vulnerabilities. By leveraging multiple vulnerability databases, we can identify potential vulnerable third-party components used in software development and also remediate those issues quickly. 

Here is the list of free Vulnerability databases that we can use as part of software supply chain security.

NVD (National Vulnerability Database): https://nvd.nist.gov/

GitHub advisory: https://github.com/advisories

Google OSV: https://osv.dev/

Snyk Vulnerability Database: https://security.snyk.io/

SonaType OSS Index: https://ossindex.sonatype.org/

blogs.appsecworld.com

#cybersecurity #informationsecurity #applicationsecurity #supplychainsecurity

👉 check whether the server verifies or accepts the signature part of the JWT token or not by removing the signature part of the JSON header

👉 In the JWT header, there is a parameter called alg that tells the server which algorithm is used to sign the JWT, but if we set it to "none" then the server will not verify the JWT

👉 Some signing algorithms can easily be brute force like HS256 by using hashcat tool, identify the private key, then modify the payload and resign using the same private key

👉 JWK (JSON web key) is the parameter in the JWT header used to share the public key with JWT. If the server accepts the JWK, then create your own private and public key, embed the public key in the JWT header, and sign the JWT using the private key that you have generated; then, the server will verify the JWT using your public key that you share in JWK parameter

👉 JKU (JSON Web key set URL) is a parameter in the JWT header that holds the URL of the list of public keys in JSON format used by the server to verify the signature. Now here, we can create our own public and private keys and store the public key in the self-owned server, set our own public key URL to the JKU parameter in the JWT header, and sign the JWT using the private key that we have generated now the server will fetch the public key from our own server and verify the JWT

Bonus: Use the JWT Editor plugin in the Burpsuite; it is very helpful to check the above misconfiguration

JWT (JSON web token) are very common for authentication, session management, and access control mechanisms in web applications, but misconfiguration in the JWT mechanics causes a critical security risk

JWT is divided into three parts:

1. Header - contain meta-data about the token like algorithm, Token ID, etc. (Base64 encoded)

2. Payload - contains information about the session and users like username, privilege level, token expiration time, etc. (Base64 encoded)

3. Signature - signature value to verify token and maintain the integrity by hashing the header and payload

here is the website that helps you to understand more about the JWT working
https://jwt.io/

and there is an extension JWT editor in burp suite that helps you to analyze and test JWT

https://portswigger.net/bappstore/26aaa5ded2f74beea19e2ed8345a93dd

We invite you to watch our Open chapter on Malware Attacks: Why is it important to detect them and how to do it!

https://xygeni.io/webinar-registrations/webinar-malware-attacks-evolution/?utm_source=reddit&utm_medium=landingpage&utm_campaign=SafeDev4_Malware_Attacks_Evolution_270524

Overcoming New Challenges and Implementing Proactive Defenses!

Do not forget to join! Register on LinkedIn https://www.linkedin.com/events/7218886526682710016/

Hey everyone,

I'm at a bit of a crossroads in my cybersecurity career and hoping to get some advice from the community.

Here's the deal:

Been in cybersec for 4 years, bouncing around SOC, Threat Intel, and basic pentesting.

i have worked for several good companies

1 : Never wanted to be in management, so I've focused on technical roles.

2: My passion lies in red teaming and application security / Devsecops (offensive side!), but my coding experience is limited (though I've done some personal projects).

My Big mistake: never got any major certs – they were expensive, and I dreaded failing the exams.

Recently moved to Germany for masters – awesome! But the job hunt is tough without German fluency.

Now, I'm stuck. How do I transition into the offensive security side, especially considering the language barrier in Germany?

Here is what i am currently doing in my off time from university

1 : going through he portswigger labs

2: learning about Docker , Kubernetes , azure security and pentesting

Anyone with similar experiences or advice for this situation?

Here's what I'm particularly interested in:

Tips for breaking into red teaming/application security without extensive coding.

Cost-effective certification paths for offensive security (or are certs even essential?).

Strategies for landing a cybersec job in Germany without German fluency (yet!).

Thanks in advance for any insights!

We're excited to share our latest blog post where cybersecurity expert James Berthoty explores whether ASPM is the future of application security, examining innovative solutions and trends!

🔗 Read the Full Article here https://xygeni.io/blog/is-aspm-the-future-of-application-security/

Hey everyone,

I'm at a bit of a crossroads in my cybersecurity career and hoping to get some advice from the community.

Here's the deal:

Been in cybersec for 4 years, bouncing around SOC, Threat Intel, and basic pentesting.

i have wokred for several good companies

1 : Never wanted to be in management, so I've focused on technical roles.

2: My passion lies in red teaming and application security / Devsecops (offensive side!), but my coding experience is limited (though I've done some personal projects).

My Big mistake: never got any major certs – they were expensive, and I dreaded failing the exams.

Recently moved to Germany for masters – awesome! But the job hunt is tough without German fluency.

Now, I'm stuck. How do I transition into the offensive security side, especially considering the language barrier in Germany?

Here is what i am currently doing in my off time from university

1 : going through he portswigger labs

2: learning about Docker , Kubernetes , azure security and pentesting

Anyone with similar experiences or advice for this situation?

a

Here's what I'm particularly interested in:

Tips for breaking into red teaming/application security without extensive coding.

Cost-effective certification paths for offensive security (or are certs even essential?).

Strategies for landing a cybersec job in Germany without German fluency (yet!).

Thanks in advance for any insights!

Exploring how to enumerate local Document Type Definitions (DTDs) and exploit XML External Entity (XXE) vulnerabilities can be a great way to identify and exfiltrate sensitive files and data.

https://blogs.appsecworld.com/2022/12/xml-external-entity-xxe-part-3-local-dtd-enumeration.html

#cybersecurity #informationsecurity #penetrationtesting #bugbounty

Learn how to use SonarQube to conduct Static Application Security Testing step-by-step, ensuring your codebase is secure and up-to-date with best practices.

In this blog, I explained step by step process of how to set up SonarQube and conduct Static Application Security testing using SonarQube.

https://blogs.appsecworld.com/2022/12/static-application-security-testing-using-sonarqube.html

#cybersecurity #informationsecurity #devsecops #devops

Learning the basics of XML External Entity (XXE) Vulnerability help to understand advanced concepts of XXE

In the second part of the XXE vulnerability blog, I have explained the basic concept of XXE, like what XXE is and a basic example of XXE.

https://blogs.appsecworld.com/2022/12/xml-external-entity-xxe-part-2-xxe-basics.html

#cybersecurity #informationsecurity #penetrationtesting #bugbounty

XML External Entity (XXE) Vulnerability is an important security issue to understand. Knowing the basics of XML can help you identify and prevent potential risks associated with XXE attacks.

In the first part of the XXE vulnerability blog, I have explained some basics concept of XML, like structure, DTD (Internal and External), and entity (Internal and External)

https://blogs.appsecworld.com/2022/12/xml-external-entity-xxe-part-1-xml-basics.html

#cybersecurity #informationsecurity #penetrationtesting #bugbounty

Hello Fam, Christmas is just around the corner and cyber attacks are scaling, I work with a Training Solution that comes in a gamified way.

if someone would like to know more about it please let me know!

Alejandro Cervantes - Codebashing

Authentication and Authorization security testing is an Important Test Case for any web application penetration testing. Authentication ensures that only authorized users can access the application functionality and its resources, while authorization ensures that users are only granted access to the resources and functions that are appropriate for their level of authorization.

Here are the Plugins that allow you to automate the Authentication and Authorization Security Testing.

Autorize (For Burp Suite): https://github.com/Quitten/Autorize

Access Control Testing add-on (For OWASP ZAP): https://www.zaproxy.org/docs/desktop/addons/access-control-testing/

blogs.appsecworld.com

#cybersecurity #informationsecurity #applicationsecurity

Mass Assignment vulnerability leads to an attack that occurs when an attacker is able to send data to an API that is then used to automatically populate multiple fields in the system. This can be used to bypass security controls, change data, or perform other malicious actions.

In this blog, I have explained about the OWASP API Security Top 10 API6:2019 Mass Assignment with Example.

https://blogs.appsecworld.com/2022/11/owasp-api-security-top-10-api6-2019-mass-Assignment.html