dbcve.org
CoverityApplication · Synopsys

CVE-2023-1663

MEDIUM · 5.3 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to 2023.3.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Coverity versions prior to 2023.3.2 are vulnerable to forced browsing, which exposes authenticated resources to unauthorized actors. The root cause of this vulnerability is an insecurely configured servlet mapping for the underlying Apache Tomcat server. As a result, the downloads directory and its contents are accessible. 5.9 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L/E:P/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 versions prior to 2023.3.2 contain an insecurely configured servlet mapping in the underlying Apache Tomcat server, allowing forced browsing to access the downloads directory and its contents without authentication. This exposes sensitive resources meant for authenticated users to unauthorized actors via direct URL access.

MitigationUpgrade Coverity to version 2023.3.2 or later, and review Tomcat servlet mappings to ensure authenticated endpoints are properly protected and not accessible via forced browsing.

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:< 2023.3.2

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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

  1. Determine installed Coverity version
    Locate and read the Coverity version file (typically found in the installation directory, such as version.txt or via the Coverity platform administration interface)
    Affected if Version is prior to 2023.3.2
  2. Identify embedded Tomcat configuration
    Find the Tomcat server.xml or web.xml configuration file within the Coverity installation directory structure
    Affected if The configuration file exists and contains servlet mappings for the downloads directory
  3. Test unauthenticated downloads access
    Attempt to access the downloads directory via direct URL (such as http://<host>:<port>/downloads/) using a browser or curl without providing any authentication credentials
    Affected if The directory contents are served and accessible without requiring login
  4. Inspect servlet mapping security constraints
    Examine the Tomcat configuration for the downloads servlet mapping and verify whether security constraints (security-constraint or auth-constraint elements) are properly defined
    Affected if The downloads servlet mapping lacks authentication constraints or allows unrestricted access

If running Coverity version prior to 2023.3.2 and the downloads directory is accessible without authentication, the environment is affected by this vulnerability

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 2023.3.2 or later
Fixed in 2023.3.2
Interim mitigation

Upgrade Coverity to version 2023.3.2 or later, and review Tomcat servlet mappings to ensure authenticated endpoints are properly protected and not accessible via forced browsing.

Recommended fix High confidence

Coverity 2023.3.2

  1. Download Coverity version 2023.3.2 or later from the Synopsys community portal
  2. Backup the existing Coverity installation and configuration
  3. Stop all Coverity services
  4. Install the upgraded Coverity version
  5. Restore the configuration from the backup
  6. Start Coverity services
  7. Verify the downloads directory is no longer accessible without authentication

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

Fix this in Coverity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1663 — 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-1663 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