Easy TestApplication · Easy Test Project

CVE-2022-43437

HIGH · 8.8 CVSS v3.1 Published 2023-01-03
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
The Download function’s parameter of EasyTest has insufficient validation for user input. A remote attacker authenticated as a general user can inject arbitrary SQL command to access, modify or delete database.

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

SQL injection vulnerability in EasyTest's Download function where insufficient input validation on a parameter allows authenticated users to inject arbitrary SQL commands, potentially enabling unauthorized access, modification, or deletion of database contents.

MitigationImplement proper input validation and replace dynamic SQL queries with parameterized queries/prepared statements in the Download function to prevent SQL injection.

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
Easy TestApplication
Affected:= 17l18s

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 EasyTest version
    Locate the installed version of Easy Test Project Easy Test in the application documentation, About page, or version file. Common locations include version.txt, setup.ini, or the application header/footer.
    Affected if The installed version equals 17l18s (or falls within the affected range if additional versions are known)
  2. Locate the Download function
    Identify where the Download function is implemented in the EasyTest application. Check the application's source code, web endpoints, or API routes for functions named 'Download', 'download', or similar file retrieval endpoints.
    Affected if The Download function exists and is accessible within the application
  3. Verify Download function is enabled
    Confirm the Download feature is enabled in the application configuration. Check config files, admin settings, or feature flags that control whether the Download function is active for users.
    Affected if The Download function is enabled and accessible to authenticated users
  4. Inspect SQL query implementation in Download function
    Examine the code handling the Download function's database queries. Look for dynamic SQL construction where user-supplied parameters are directly concatenated into SQL statements without proper escaping or parameterization.
    Affected if The Download function uses dynamic SQL queries with direct parameter concatenation rather than parameterized queries or prepared statements
  5. Check authentication context
    Determine if the Download function is accessible to authenticated users. Review access control settings and authentication requirements for this endpoint.
    Affected if The Download function can be accessed by authenticated users without additional security controls on the SQL-relevant parameter

You are affected if running Easy Test version 17l18s with the Download function enabled and the SQL query implementation uses direct parameter concatenation rather than parameterized queries.

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

Implement proper input validation and replace dynamic SQL queries with parameterized queries/prepared statements in the Download function to prevent SQL injection.

Fix this in Easy Test Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43437 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-43437 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