# CVE-2023-27647: Information disclosure in n/a

> A local attacker can cause denial of service or access sensitive information in DUALSPACE Lock Master via improper content provider permissions.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2023
- **Updated:** 10 Feb 2025
- **Also known as:** GHSA-r295-r6mq-x42c

## What is CVE-2023-27647?

CVE-2023-27647 is a high-severity vulnerability in n/a, published on 14 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue found in DUALSPACE Lock Master v.2.2.4 allows a local attacker to cause a denial of service or gain sensitive information via the com.ludashi.superlock.util.pref.SharedPrefProviderEntryMethod: insert of the android.net.Uri.insert method.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2023-27647?

It affects 1 product.


Products: Dualspace Lock Master.

## How do I fix CVE-2023-27647?

No fix has been published for CVE-2023-27647 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-27647 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27647 exists.

## Other vulnerabilities in n/a

- [CVE-2023-29733](https://insights.sbomify.com/CVE-2023-29733/): Missing authorization in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-27647 and fix it if it is affected.

What it is: CVE-2023-27647 is a high-severity vulnerability in n/a, published on 14 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27647 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-27647/ (Markdown: https://insights.sbomify.com/CVE-2023-27647/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-27647
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-27647
- OSV: https://osv.dev/vulnerability/CVE-2023-27647

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-27647/
Summaries are generated and may contain mistakes; the official description above is the record.