dbcve.org
Network RegistrarApplication · Cisco

CVE-2019-1852

MEDIUM · 6.1 CVSS v3.0 Published 2019-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A vulnerability in the web-based management interface of Cisco Prime Network Registrar could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web-based interface. The vulnerability is due to insufficient validation of user-supplied input by the web-based management interface. An attacker could exploit this vulnerability by persuading a user of the interface to click a malicious link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the interface or allow the attacker to access sensitive browser-based 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 confidence

A cross-site scripting (XSS) vulnerability in the web-based management interface of Cisco Prime Network Registrar allows unauthenticated, remote attackers to inject malicious scripts via insufficiently validated user-supplied input. Successful exploitation enables arbitrary script execution in the context of the interface or access to sensitive browser-based information.

MitigationApply the Cisco patch for CVE-2019-1852. In the interim, users should avoid clicking untrusted links to the management interface.

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
Network RegistrarApplication
Affected:= 9.1\(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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/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. Identify if Cisco Network Registrar is installed
    Check for the presence of Cisco Network Registrar on the system. Common installation paths include /opt/cisco/network-registrar or check system services for 'cnpnr' or 'network-registrar' processes. On Windows, check Program Files for Cisco Network Registrar.
    Affected if Cisco Network Registrar is not installed on the system.
  2. Determine the installed version
    If installed, check the version. Typically found in the web interface login page header, or via CLI command 'show version' if accessing the management console, or check version files in the installation directory such as VERSION.txt or a .version file in the base installation path.
    Affected if The installed version is Cisco Network Registrar 9.1(2).
  3. Confirm web-based management interface is enabled
    Check if the web-based management interface service is running and accessible. This is typically on ports 8080 or 8443 (HTTP/HTTPS). Verify the service process is active and the ports are listening.
    Affected if The web-based management interface is accessible and responds to requests.
  4. Inspect web interface for input validation
    Access the web-based management interface login page and examine the HTML source or attempt to submit special characters (< > " ') in input fields to observe if they are reflected without proper encoding.
    Affected if User-supplied input is reflected in responses without sanitization or encoding.

The environment is affected if Cisco Network Registrar version 9.1(2) is installed and its web-based management interface is enabled and accessible.

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

Apply the Cisco patch for CVE-2019-1852. In the interim, users should avoid clicking untrusted links to the management interface.

Fix this in Network Registrar Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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