Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

common vulnerability and exposures checking for java program!

Ranch Hand
Posts: 630
Android Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I read about Common Vulnerabilities and Exposures.
I download its pdf also.
Is there any one used these things?
I used Static Analysis tools for my projects/programs.
But I not used 'Common Vulnerabilities and Exposures'.

I think if properly study & then coding, then our program will be complete safe from 'Common_Vulnerabilities_and_Exposures'.
But confusion about those 'CVE-ID' things...

Is there any tool/plugin in IDE which helps to find out which Vulnerabilities and Exposures with specific CVE-ID we have in program or project!
So after editing program it will become clear.

Can somebody give me guidance.
Posts: 15884
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
CVEs cover all things related to vulnerabilities and exposures in software, not just Java, and yes, many companies actually use these although I doubt anyone has the time or need to look at all of them. I just did a search on the NVD for "Java" and got back 1,542 matches out of 76,362 CVE entries. These numbers are constantly growing, although the total will grow faster than the ones for specific technologies.

The products I support are related to security intelligence and management of security-related work in operations so I'm quite familiar with CVE numbers. They are standard identifiers across the industry so that a specific security issue can be referred to consistently across systems and product/service offerings from different companies.

As for tooling, you can start by looking through recommendations from OWASP:
Mandar Khire
Ranch Hand
Posts: 630
Android Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Junilu Lacar,
First of all sorry for asking question in wrong section of this forum.
I observe that many developer use Code analysis but it only for basic problem solving.
I used SonarLint for my project but never read about CVE.
When I realize that I should make safer code by studying CVE but project might be delay & as per client its not so much worthy that make most secure (might client also not aware CVE!).
So I am writing small article based on various whitepapers/blogs/articles/discussions/books for awareness of CVE which will might become useful for developer those working on various projects but not following guidelines for various types of securities.
Sasparilla and fresh horses for all my men! You will see to it, won't you tiny ad?
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic