dbcve.org
PricepointApplication · Vendavo

CVE-2017-20042

HIGH · 8.8 CVSS v3.1 Published 2022-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 vulnerability has been found in Navetti PricePoint 4.6.0.0 and classified as critical. Affected by this vulnerability is an unknown functionality. The manipulation leads to sql injection (Blind). The attack can be launched remotely. Upgrading to version 4.7.0.0 is able to address this issue. It is recommended to upgrade the affected component.

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

Navetti PricePoint 4.6.0.0 contains a blind SQL injection vulnerability in an unspecified functionality. The flaw allows remote attackers to inject malicious SQL queries via unsanitized input, potentially allowing data exfiltration or database compromise. This is a classic injection flaw exploitable without authentication.

MitigationUpgrade to Navetti PricePoint 4.7.0.0 which contains the patched code. Prior to production deployment, validate the upgrade in a staging environment and confirm input validation is properly enforced across all user-facing fields.

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
PricepointApplication
Affected:= 4.6.0.0

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
High
Integrity
High
Availability
High

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

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

  1. Identify Navetti PricePoint installation
    Locate the Navetti PricePoint or Vendavo Pricepoint application in your environment. Check for the pricepoint application directory, service, or web application folder.
    Affected if Navetti PricePoint version 4.6.0.0 is installed and running
  2. Determine installed version
    Inspect the application version information. Check the software's about page, version file, manifest, or the version string returned by the application. Compare your installed version to the affected range.
    Affected if The installed version is exactly 4.6.0.0
  3. Assess network accessibility
    Determine if the PricePoint web interface is accessible over the network. Identify the listening port and URL path.
    Affected if The application is network-accessible and version 4.6.0.0 is confirmed
  4. Identify SQL injection entry points
    Review the web application's input fields and parameters. Since the vulnerability is in unspecified functionality, document all user-facing input parameters.
    Affected if The application accepts user input and runs version 4.6.0.0

If your environment is running Navetti PricePoint or Vendavo Pricepoint version exactly 4.6.0.0, you are affected by this blind SQL injection 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Navetti PricePoint 4.7.0.0 which contains the patched code. Prior to production deployment, validate the upgrade in a staging environment and confirm input validation is properly enforced across all user-facing fields.

Recommended fix High confidence

4.7.0.0

  1. Backup the current Navetti PricePoint 4.6.0.0 installation and database before proceeding
  2. Download Navetti PricePoint version 4.7.0.0 from the official vendor (Navetti)
  3. Review the vendor's upgrade documentation for PricePoint 4.7.0.0
  4. Test the upgrade in a non-production/staging environment first
  5. Apply the upgrade following the vendor's documented upgrade procedure
  6. Verify the SQL injection vulnerability is resolved by testing the previously vulnerable functionality
  7. Deploy the updated version to production
Caveat No breaking changes documented in the provided vulnerability description

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

Fix this in Pricepoint Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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