Jsecurity vulnerabilitiesNone on the known-exploited list.
Jsecurity has 1 published vulnerability across 1 product in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Jsecurity, with 1. If you run Jsecurity software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Jsecurity products have the most vulnerabilities?
Jsecurity leads with 1 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Jsecurity vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Jsecurity's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Jsecurity flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 55%CVE-2010-3863Medium
Apache Shiro before 1.1.0, and JSecurity 0.9.x, does not canonicalize URI paths before comparing them to entries in the shiro.ini file, which allows remote attackers to bypass intended access restrictions via a...
All Jsecurity products we track.
1 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Jsecurity? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Apache Shiro before 1.1.0, and JSecurity 0.9.x, does not canonicalize URI paths before comparing them to entries in the shiro.ini file, which allows remote attackers to bypass intended access restrictions via a crafted request, as demonstrated by the /./account/index.jsp URI.
- Matched to
- Jsecurity on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 1 published vulnerability across 1 product and 1 version from Jsecurity.
None of Jsecurity's vulnerabilities is on the list of flaws known to be exploited today.
Jsecurity, with 1 published vulnerability. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Jsecurity products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.