CVE-2023-27197
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 A930 device with PayDroid_7.1.1_Virgo_V04.5.02_20220722 can allow an attacker to gain root access by running a crafted binary leveraging an exported function from a shared library. The attacker must have shell access to the device in order to exploit this vulnerability.
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 A930 payment terminal running PayDroid_7.1.1_Virgo_V04.5.02_20220722 contains a local privilege escalation vulnerability. An attacker with existing shell access can run a crafted binary that exploits an exported function in a shared library to gain root privileges on the device.
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.
-
Identify the device firmware versionRun 'getprop ro.build.display.id' or check /system/build.prop to retrieve the exact firmware version stringAffected if The version string is exactly 'paydroid_7.1.1_virgo_v04.5.02_20220722'
-
Confirm shell access is availableVerify if the device allows shell command execution via ADB, telnet, SSH, or any other remote access mechanismAffected if Shell or command execution access is exposed to any user or network beyond authorized personnel
-
Locate exported functions in shared librariesInspect the /system/lib or /vendor/lib directories for shared libraries (.so files) and use 'nm -D' or 'readelf -s' to list exported functionsAffected if A shared library contains an exported function that can be invoked to achieve privilege escalation
-
Check for presence of the exploit binarySearch the filesystem for any unknown or recently created executable binaries in locations such as /data/local/tmp, /tmp, or other writable directoriesAffected if An unknown crafted binary exists on the device that could trigger the vulnerable exported function
The device is affected if it runs firmware version paydroid_7.1.1_virgo_v04.5.02_20220722 AND shell access is available to an attacker who could leverage a shared library exported function for root escalation.
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 dataRestrict shell access to authorized personnel, apply any vendor firmware updates from PAX, and if the vulnerable exported function is not required for legitimate operations, disable or remove it from the shared library.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27197 — 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-27197 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