CVE-2023-27199
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 · uneditedPAX Technology A930 PayDroid_7.1.1_Virgo_V04.5.02_20220722 allows attackers to compile a malicious shared library and use LD_PRELOAD to bypass authorization checks.
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 confidenceThe PAX Technology A930 payment terminal running PayDroid_7.1.1 contains a vulnerability where attackers can compile a malicious shared library and use the LD_PRELOAD environment variable to preload it, allowing bypass of authorization checks. This is a local privilege escalation/authorization bypass vulnerability affecting the embedded Linux-based payment terminal firmware.
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= paydroid_7.1.1_virgo_v04.5.02_20220722CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device is a PAX A930 terminalIdentify the payment terminal model through device information, labeling, or system queriesAffected if Device is not a PAX A930 model
-
Check the installed firmware versionRetrieve the firmware version from the device and compare it exactly to paydroid_7.1.1_virgo_v04.5.02_20220722Affected if Firmware version is paydroid_7.1.1_virgo_v04.5.02_20220722
-
Determine if LD_PRELOAD can be setTest whether the LD_PRELOAD environment variable can be defined and is honored by the dynamic linker when executing binariesAffected if LD_PRELOAD is functional and not restricted or disabled
-
Assess local access exposureEvaluate whether an attacker could obtain local access to set environment variables and load malicious librariesAffected if Device is physically accessible to untrusted users
-
Check if authorization relies on preloadable librariesIdentify whether security-critical authorization logic uses shared libraries that could be intercepted via LD_PRELOADAffected if Authorization mechanisms load vulnerable shared libraries
The environment is affected if it is a PAX A930 terminal running firmware paydroid_7.1.1_virgo_v04.5.02_20220722 where LD_PRELOAD remains functional and a local attacker can exploit it to bypass authorization checks.
Generated from the published advisory. Verify against your own configuration.
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 dataDisable or restrict the LD_PRELOAD environment variable in the PayDroid system, implement strict seccomp/AppArmor policies to prevent preload hijacking, and apply vendor firmware updates to address the authorization bypass. Physical access controls should be enforced to prevent local attackers from loading malicious libraries.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27199 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-27199 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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