# What is CVE-2016-6812? > CVE-2016-6812 is a medium-severity flaw (CVSS 6.1) in Cxf from Apache, published on 10 August 2017. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 7.5%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2016-6812 ## At a glance - **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle. - **Precursor Intelligence risk score:** 46 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes. - **Severity:** Medium (CVSS 6.1 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 7.5% (latest exploit-likelihood forecast) - **Published:** 10 August 2017 - **Record last updated:** 20 April 2025 - **Main product:** Cxf from Apache - **Affected products:** 1 ## What is CVE-2016-6812? In plain terms It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read some data and change some data. ### The official description The HTTP transport module in Apache CXF prior to 3.0.12 and 3.1.x prior to 3.1.9 uses FormattedServiceListWriter to provide an HTML page which lists the names and absolute URL addresses of the available service endpoints. The module calculates the base URL using the current HttpServletRequest. The calculated base URL is used by FormattedServiceListWriter to build the service endpoint absolute URLs. If the unexpected matrix parameters have been injected into the request URL then these matrix parameters will find their way back to the client in the services list page which represents an XSS risk to the client. ### What kind of flaw is it? - CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') ### How an attack on it works - Where an attacker can be: Anywhere on the internet - How hard it is to pull off: Easy: no special conditions - Login needed first: No login needed - Does someone have to click: Yes, a person has to take an action - What an attacker gets: Can read some data and change some data Severity vector: `CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N` ## Is CVE-2016-6812 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 7.5%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 7.5%, 7.5%, 7.5%, 7.5%, 7.5%, 7.5%, 7.5%. ### Timeline - 10 August 2017: Published - 20 April 2025: Record last updated ### How Precursor Intelligence ranks it CVE-2016-6812 scores **46 out of 100 (Medium)**, with the action "Plan remediation". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2016-6812? The published record lists 1 product. - [Cxf](https://www.precursorintelligence.com/product/apache/cxf) by [Apache](https://www.precursorintelligence.com/vendors/apache) (Application): up to 3.0.11, 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.1.6, 3.1.7, 3.1.8 ## How do I fix CVE-2016-6812? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [cxf.apache.org](http://cxf.apache.org/security-advisories.data/CVE-2016-6812.txt.asc) (Patch, Vendor advisory) - [issues.apache.org](https://issues.apache.org/jira/browse/CXF-6216) (Issue tracking, Vendor advisory) - [securityfocus.com](http://www.securityfocus.com/bid/97582) (Third-party advisory, Vulnerability database) - [securitytracker.com](http://www.securitytracker.com/id/1037543) (Third-party advisory, Vulnerability database) - [access.redhat.com](https://access.redhat.com/errata/RHSA-2017:0868) - [lists.apache.org](https://lists.apache.org/thread.html/r36e44ffc1a9b365327df62cdfaabe85b9a5637de102cea07d79b2dbf%40%3Ccommits.cxf.apache.org%3E) - [lists.apache.org](https://lists.apache.org/thread.html/rc774278135816e7afc943dc9fc78eb0764f2c84a2b96470a0187315c%40%3Ccommits.cxf.apache.org%3E) - [lists.apache.org](https://lists.apache.org/thread.html/rd49aabd984ed540c8ff7916d4d79405f3fa311d2fdbcf9ed307839a6%40%3Ccommits.cxf.apache.org%3E) - [lists.apache.org](https://lists.apache.org/thread.html/rec7160382badd3ef4ad017a22f64a266c7188b9ba71394f0d321e2d4%40%3Ccommits.cxf.apache.org%3E) - [lists.apache.org](https://lists.apache.org/thread.html/rfb87e0bf3995e7d560afeed750fac9329ff5f1ad49da365129b7f89e%40%3Ccommits.cxf.apache.org%3E) - [lists.apache.org](https://lists.apache.org/thread.html/rff42cfa5e7d75b7c1af0e37589140a8f1999e578a75738740b244bd4%40%3Ccommits.cxf.apache.org%3E) ## Questions ### What is CVE-2016-6812? CVE-2016-6812 is a medium-severity flaw in Cxf from Apache, published on 10 August 2017. It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read some data and change some data. ### How serious is CVE-2016-6812? It scores 6.1 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2016-6812 is 46 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle. ### Is CVE-2016-6812 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 7.5%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2016-6812 affect? For Cxf from Apache: up to 3.0.11, 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4 and 4 more. ### How do I fix CVE-2016-6812? Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2016-6812 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact