CVE-2011-3609 json
A CSRF issue was found in JBoss Application Server 7 before 7.1.0.
published 2019-11-26 6 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3568
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
A CSRF issue was found in JBoss Application Server 7 before 7.1.0. JBoss did not properly restrict access to the management console information (for example via the "Access-Control-Allow-Origin" HTTP access control flag). This can lead to unauthorized information leak if a user with admin privileges visits a specially-crafted web page provided by a remote attacker.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2011-3609 updated cvss 2.6
AS: CSRF in the administration console & HTTP management API
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.31% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Affected products
- JBoss Application Server JBoss Application Server
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
security-tracker.debian.org
/tracker/CVE-2011-3609
third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2011-3609
issue-tracking, third-party-advisory
-
access.redhat.com
/security/cve/cve-2011-3609
third-party-advisory
-
securityfocus.com
/bid/50888
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2011-3609
- NVD CVE-2011-3609
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.