# CVE-2014-1217: Missing authorization in n/a

> Remote attackers can access system settings to modify configurations and steal database credentials due to missing authorization checks.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5263-f497-fhwq

## What is CVE-2014-1217?

CVE-2014-1217 is a high-severity missing authorization vulnerability in n/a, published on 28 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Livetecs Timelive before 6.2.8 does not properly restrict access to systemsetting.aspx, which allows remote attackers to change configurations and obtain the database connection string and credentials via unspecified vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2014-1217?

It affects 1 product.


Products: Livetecs Timeline.

## How do I fix CVE-2014-1217?

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

## Is CVE-2014-1217 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2042](https://insights.sbomify.com/CVE-2014-2042/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1217 and fix it if it is affected.

What it is: CVE-2014-1217 is a high-severity missing authorization vulnerability in n/a, published on 28 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-1217 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-2014-1217/ (Markdown: https://insights.sbomify.com/CVE-2014-1217/index.md)
```

## Sources

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

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