dbcve.org
CoverityApplication · Synopsys

CVE-2023-23849

MEDIUM · 6.1 CVSS v3.1 Published 2023-02-06
Fix available
A fix is available. Upgrade to 2022.12.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Versions of Coverity Connect prior to 2022.12.0 are vulnerable to an unauthenticated Cross-Site Scripting vulnerability. Any web service hosted on the same sub domain can set a cookie for the whole subdomain which can be used to bypass other mitigations in place for malicious purposes. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/RL:O/RC:C

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 confidence

Coverity Connect versions prior to 2022.12.0 contain an unauthenticated cross-site scripting (XSS) vulnerability where any web service hosted on the same subdomain can set cookies for the entire subdomain, enabling bypass of existing security mitigations for malicious purposes.

MitigationUpgrade Coverity Connect to version 2022.12.0 or later to obtain the official fix for this vulnerability.

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
CoverityApplication
Affected:< 2022.12.0

CVSS 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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine the installed Coverity Connect version
    Access the Coverity Connect administration interface or check the installation metadata (commonly found in version files, about pages, or the installation directory). Compare the version number to the 2022.12.0 release.
    Affected if The installed version is any release prior to 2022.12.0 (e.g., 2022.9.0, 2022.6.0, etc.)
  2. Identify all web services hosted on the same subdomain as Coverity Connect
    Review the DNS records and web server configurations to enumerate all applications and services accessible within the same subdomain namespace (e.g., coverity.example.com, otherapp.example.com).
    Affected if Any additional web services exist on the same subdomain as the Coverity Connect instance
  3. Verify cookie security configuration for the subdomain
    Inspect the HTTP response headers from the Coverity Connect server, specifically looking for Set-Cookie directives and their attributes (Secure, HttpOnly, SameSite). Also check if the domain attribute is set to a broad subdomain.
    Affected if Cookies are set with a broad subdomain domain attribute or lack appropriate SameSite and Secure flags, allowing other services on the subdomain to influence them
  4. Check for unauthenticated access to web service endpoints
    Attempt to access Coverity Connect web interfaces without authentication credentials. Review access logs for unauthenticated requests to API or web endpoints.
    Affected if The Coverity Connect web interface accepts requests without requiring authentication, enabling the XSS attack vector

A system is affected if it runs any version of Coverity Connect prior to 2022.12.0 and has other web services or unprotected endpoints on the same subdomain, allowing cookie manipulation for XSS exploitation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2022.12.0 or later
Fixed in 2022.12.0
Interim mitigation

Upgrade Coverity Connect to version 2022.12.0 or later to obtain the official fix for this vulnerability.

Recommended fix High confidence

Coverity Connect 2022.12.0

  1. Verify current Coverity Connect version by checking the About page or running 'coverity --version'
  2. Review the Coverity 2022.12.0 release notes for upgrade requirements and migration considerations
  3. Take a full backup of the Coverity database and configuration files
  4. Stop all Coverity services before upgrading
  5. Upgrade to Coverity Connect version 2022.12.0 or later using the standard installation process
  6. Restart Coverity services after upgrade completion
  7. Verify the upgrade was successful and the application is functioning correctly
  8. Confirm the version is now 2022.12.0 or later
Caveat Review 2022.12.0 release notes for any configuration or migration changes; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Coverity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23849 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-23849 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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