dbcve.org
Audit To DatabaseDatabase / datastore · Jenkins

CVE-2019-1003077

MEDIUM · 6.5 CVSS v3.1 Published 2019-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
A missing permission check in Jenkins Audit to Database Plugin in the DbAuditPublisherDescriptorImpl#doTestJdbcConnection form validation method allows attackers with Overall/Read permission to initiate a connection to an attacker-specified server.

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

The Jenkins Audit to Database Plugin has a missing permission check in the DbAuditPublisherDescriptorImpl#doTestJdbcConnection form validation method. Attackers with default Overall/Read permission can abuse this to initiate JDBC connections to attacker-controlled servers, enabling Server-Side Request Forgery (SSRF) for network reconnaissance or data exfiltration.

MitigationAdd permission checks (e.g., using Jenkins' StaplerPermission check or appropriate permission requirements) to the doTestJdbcConnection method to ensure only authorized users can test database connections and cannot specify arbitrary server targets.

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
Audit To DatabaseDatabase / datastore
Affected:all versions

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Verify Audit to Database plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the CLI: jenkins-cli.jar or REST API GET /pluginManager/plugin/audit-to-database
    Affected if The plugin appears in the installed plugins list
  2. Check plugin version
    Look up the plugin version in the Installed Plugins table, or query GET /pluginManager/plugin/audit-to-database/api/json
    Affected if Any version is returned (all versions are affected)
  3. Identify the vulnerable endpoint
    Check if the endpoint /descriptor/au.com.interlated.audit.db.DbAuditPublisherDescriptorImpl/doTestJdbcConnection is accessible
    Affected if The endpoint responds without requiring admin-level permissions
  4. Test permission requirement
    Submit a test JDBC connection request as a user with only Overall/Read permission (or as anonymous), e.g., POST to /descriptor/au.com.interlated.audit.db.DbAuditPublisherDescriptorImpl/doTestJdbcConnection with jdbcUrl parameter pointing to a test server
    Affected if The request succeeds or returns a validation response instead of a permission denied error
  5. Review form validation method code
    Examine the plugin's DbAuditPublisherDescriptorImpl class for the doTestJdbcConnection method - verify if @Restricted or permission annotations are present
    Affected if The method lacks permission checks such as @RequirePOST with appropriate permission requirements or StaplerPermission checks

If the Audit to Database plugin is installed and the doTestJdbcConnection endpoint responds without requiring admin-level permissions, the environment is vulnerable to SSRF.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add permission checks (e.g., using Jenkins' StaplerPermission check or appropriate permission requirements) to the doTestJdbcConnection method to ensure only authorized users can test database connections and cannot specify arbitrary server targets.

Fix this in Audit To Database Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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