Improper AuthenticationWeakness · CWE-287

CVE-2023-49340

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An issue was discovered in Newland Nquire 1000 Interactive Kiosk version NQ1000-II_G_V1.00.011, allows remote attackers to escalate privileges and bypass authentication via incorrect access control in the web management portal.

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

Access control vulnerability in the web management portal of Newland Nquire 1000 Interactive Kiosk (firmware NQ1000-II_G_V1.00.011) allows remote unauthenticated attackers to bypass authentication and escalate privileges to administrative level due to incorrect access control implementation.

MitigationApply vendor firmware patch when available; until then, restrict network exposure of the management portal via firewall rules, VPN access, or network segmentation, and monitor for unauthorized access attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 device model and firmware version
    Access the kiosk's system information page or check the boot screen/marketing materials for the model (Nquire 1000) and firmware version (NQ1000-II_G_V1.00.011). Alternatively, check the web management portal footer or admin panel for the version string.
    Affected if The device is a Newland Nquire 1000 Interactive Kiosk running firmware version NQ1000-II_G_V1.00.011.
  2. Determine if web management portal is network-accessible
    Attempt to access the web management portal from an untrusted network segment (for example, curl or visit http://[kiosk-ip]/ or the known management path). If the portal responds without requiring authentication, it indicates the vulnerability may be present.
    Affected if The web management portal is reachable from an untrusted network without authentication.
  3. Verify authentication is enforced on management endpoints
    Send HTTP requests to common admin endpoints (such as /admin/, /cgi-bin/, /api/admin/, or login forms) from an unauthenticated context. Check if any endpoint returns admin functionality, user lists, or configuration options without first presenting a login challenge.
    Affected if Any administrative endpoint or function is accessible without valid credentials.
  4. Inspect for unauthorized admin accounts
    If access is gained, examine the user management section of the web portal for unexpected accounts with administrative privileges, or review system logs for account creation events from unknown sources.
    Affected if New or unexpected admin-level accounts exist that were not created by legitimate administrators.

You are affected if the device is a Newland Nquire 1000 kiosk running firmware NQ1000-II_G_V1.00.011 and the web management portal is accessible from an untrusted network without requiring authentication.

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 vendor firmware patch when available; until then, restrict network exposure of the management portal via firewall rules, VPN access, or network segmentation, and monitor for unauthorized access attempts.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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