Win a copy of Microservices Testing (Live Project) this week in the Spring 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

can maven verify patch level of third party jar files

Ranch Hand
Posts: 820
IntelliJ IDE VI Editor Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

I'm looking for a way to verify that the jar files in a web application have had the latest securty patches applied.
For example, Struts 2 versions before Struts have a security hole (

I'm looking for an automated way to scan an existing, deployed war file for this and other outdated jar versions.

Eventually the goal is to integrate this scan into our build sequence.
Saloon Keeper
Posts: 25816
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
"Patch levels" for Maven-controlled projects are somewhat of a contradiction. Maven is based on the idea of discrete versions of artefacts, not on versions+patches. Patches in the old-fashioned where you could just do a brute-force binary zap are virtually unheard of any more (in part because in modern-day systems, the compilers optimize intensely on every source change).

If you wanted to scan a produced artefact for component versions, I suppose you could create a mojo for that, but it seems like it would probably be simpler to merely change the dependency versions in the POM to their required levels and do a maven clean/rebuild.
Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic