dbcve.org
IntravueApplication · Network Vision

CVE-2015-0977

HIGH · 10.0 CVSS v2.0 Published 2015-02-27
Fix available
A fix is available. Upgrade to after 2.3.0a11 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Network Vision IntraVue before 2.3.0a14 on Windows allows remote attackers to execute arbitrary OS commands via unspecified vectors.

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 confidence

Network Vision IntraVue before version 2.3.0a14 on Windows contains a critical vulnerability allowing remote attackers to execute arbitrary operating system commands. The CVSS score of 10 indicates a pre-authentication command injection flaw that can be exploited over the network without requiring credentials, giving attackers full control of the affected Windows host.

MitigationUpgrade Network Vision IntraVue to version 2.3.0a14 or later to remediate this vulnerability. As an interim control, restrict network access to the IntraVue service via firewall rules or network segmentation to prevent unauthorized remote attackers from reaching the vulnerable application.

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
IntravueApplication
Affected:<= 2.3.0a11

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 IntraVue is installed
    Check Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'IntraVue' or 'Network Vision IntraVue', or look for the IntraVue installation directory (commonly C:\Program Files\IntraVue or C:\IntraVue)
    Affected if The software is not found on the system, meaning it is not installed and not affected
  2. Determine installed IntraVue version
    Open the Windows registry key HKLM\SOFTWARE\IntraVue or check the version info in the IntraVue installation directory for a file named version.txt, about.html, or the main executable properties
    Affected if The version displayed is 2.3.0a11 or lower, or if no version can be determined and IntraVue is present
  3. Verify the service is running and network-accessible
    Open Windows Services (services.msc) and locate the IntraVue service to confirm it is running. Use 'netstat -an | findstr' to check if IntraVue ports (typically 8080, 8443, or the configured HTTP/HTTPS port) are listening on external interfaces
    Affected if The IntraVue service is running and bound to 0.0.0.0 or a publicly accessible IP address, exposing the vulnerable service to the network
  4. Confirm pre-authentication access
    Attempt to access the IntraVue web interface remotely (http://target:port) without providing credentials. If the login page or any application functionality is accessible without authentication, the command injection flaw can be exploited
    Affected if The web interface is reachable without authentication, meaning an unauthenticated remote attacker can reach the vulnerable endpoint

If Network Vision IntraVue version 2.3.0a11 or earlier is installed and the service is network-accessible, the system is vulnerable to remote command execution via pre-authentication command injection.

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 a release after 2.3.0a11
Interim mitigation

Upgrade Network Vision IntraVue to version 2.3.0a14 or later to remediate this vulnerability. As an interim control, restrict network access to the IntraVue service via firewall rules or network segmentation to prevent unauthorized remote attackers from reaching the vulnerable application.

Recommended fix High confidence

2.3.0a14 or later

  1. 1. Back up the current IntraVue configuration and any critical data
  2. 2. Obtain the fixed version (2.3.0a14 or later) from the vendor or official distribution channel
  3. 3. Stop the IntraVue service on the Windows server
  4. 4. Install version 2.3.0a14 or later following the vendor's standard upgrade procedure
  5. 5. Restart the IntraVue service
  6. 6. Verify the installation by checking the software version in the application UI or about page
  7. 7. Test that the application functions normally and command injection vulnerability is resolved

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

Fix this in Intravue Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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