FuseApplication · Redhat
CVE-2019-14860
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIt was found that the Syndesis configuration for Cross-Origin Resource Sharing was set to allow all origins. An attacker could use this lack of protection to conduct phishing attacks and further access unauthorized information.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSyndesis had CORS (Cross-Origin Resource Sharing) configuration set to allow all origins via the Access-Control-Allow-Origin header with a wildcard (*). This insecure configuration permits any external website to make cross-origin requests to the Syndesis API, enabling attackers to potentially conduct phishing attacks and access unauthorized information by tricking authenticated users into visiting malicious pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FuseApplication
< 7.5.0
SyndesisApplication
all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Syndesis or Red Hat Fuse is installedCheck for Syndesis or Fuse installations by looking for process names (syndesis, fuse) or checking common installation directories such as /opt/syndesis, /opt/fuse, or the user's home directory for .syndesis folders. Also check for containers labeled syndesis or fuse.Affected if Syndesis or Red Hat Fuse is found running or installed on the system
-
Locate CORS configuration filesSearch for configuration files that may contain CORS settings. Look for files named application.properties, application.yml, or similar configuration files within the Syndesis/Fuse installation directory. Also search for files containing 'Access-Control-Allow-Origin' or 'cors' keywords using grep or a file search utility.Affected if CORS configuration files exist in the Syndesis or Fuse installation
-
Check for wildcard CORS origin settingExamine the identified CORS configuration files and look for the Access-Control-Allow-Origin header setting. Search specifically for a value of '*' (asterisk/wildcard) being used as the allowed origin.Affected if The Access-Control-Allow-Origin header is set to '*' (wildcard) in the configuration
-
Verify web server CORS settingsIf Syndesis runs behind a web server (Apache, Nginx, Undertow), check the web server configuration for CORS headers. Look in httpd.conf, nginx.conf, or undertow configuration for any Access-Control-Allow-Origin directives with wildcard values.Affected if A web server proxy in front of Syndesis has CORS configured with a wildcard origin
-
Inspect runtime CORS headersIf the application is running, make an HTTP OPTIONS request to the Syndesis API endpoints and inspect the response headers. Specifically check the Access-Control-Allow-Origin header in the response.Affected if The running application returns Access-Control-Allow-Origin: * in HTTP responses
The environment is affected if Syndesis or Red Hat Fuse (below version 7.5.0) is installed and the CORS configuration has Access-Control-Allow-Origin set to the wildcard '*' character, allowing any external origin to make cross-origin requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data7.5.0
Configure CORS to explicitly allow only trusted, specific origin domains rather than the wildcard (*). Validate the Origin header against an allowlist and ensure proper Access-Control-Allow-Credentials handling.
Fix this in Fuse
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14860 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-14860 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data