CVE-2019-7238
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 · uneditedSonatype Nexus Repository Manager before 3.15.0 has Incorrect Access Control.
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 · moderate confidenceThis is a pre-authentication incorrect access control vulnerability in Sonatype Nexus Repository Manager. The CVSS 9.8 score indicates that unauthenticated remote attackers can bypass access controls to access sensitive functionality without any credentials.
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>= 3.0.0, < 3.15.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate the Nexus Repository Manager versionAccess the web interface and navigate to Administration > Support > About, or check the version via the command line using 'grep -r "version" <nexus_installation_dir>/nexus/etc/nexus.properties' or the 'bin/nexus --version' command if availableAffected if The version displayed is 3.0.0 or later but earlier than 3.15.0
-
Confirm the installation is accessibleVerify that the Nexus web interface is reachable over HTTP/HTTPS on the configured port (default 8081 or 8082)Affected if The web interface is exposed and responds to requests
-
Verify the permission configurationCheck that the anonymous access feature is enabled (Administration > Security > Anonymous Access) and that the default anonymous user has any meaningful permissions assignedAffected if Anonymous access is enabled and the anonymous user has been granted any role or permission beyond read-only or no access
A Nexus Repository Manager installation is affected if its installed version falls between 3.0.0 and 3.14.9 inclusive and the web interface is accessible to unauthenticated users.
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.
dbcve · scoped3.15.0
Upgrade Nexus Repository Manager to version 3.15.0 or later to remediate this vulnerability.
Nexus Repository Manager 3.15.0 or later
- Verify current Nexus Repository Manager version by accessing the web interface or checking the system information
- Backup the current Nexus installation directory, data directory, and database (if using external DB)
- Download Nexus Repository Manager version 3.15.0 or later from the official Sonatype download page
- Stop the Nexus Repository Manager service
- Extract the new version to the installation directory, preserving configuration files
- If using an external database, ensure database compatibility with the new version
- Start the Nexus Repository Manager service
- Verify the upgrade was successful by checking the version in the web interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7238 — 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-7238 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