# CVE-2013-0148: Weak cryptography in n/a

> Attackers can read cleartext database records by copying the database to a system with default configuration, bypassing encryption requirements.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-wr26-78p7-gpjj

## What is CVE-2013-0148?

CVE-2013-0148 is a high-severity vulnerability in n/a, published on 16 Jun 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Data Camouflage (aka FairCom Standard Encryption) algorithm in FairCom c-treeACE does not ensure that a decryption key is needed for accessing database contents, which allows context-dependent attackers to read cleartext database records by copying a database to another system that has a certain default configuration.

Weakness: CWE-310

## Which versions are affected by CVE-2013-0148?

It affects 1 product.


Products: Faircom C-Treeace.

## How do I fix CVE-2013-0148?

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

## Is CVE-2013-0148 being exploited?

There is no known exploitation of CVE-2013-0148 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-0148 and fix it if it is affected.

What it is: CVE-2013-0148 is a high-severity vulnerability in n/a, published on 16 Jun 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-0148 in the wild and no public exploit code.

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-2013-0148/ (Markdown: https://insights.sbomify.com/CVE-2013-0148/index.md)
```

## Sources

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

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