# CVE-2013-3540: Cross-site request forgery in n/a

> Remote attackers can hijack administrator sessions via CSRF to add unauthorized users on AirLive IP cameras.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Oct 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xj4q-493h-q98m

## What is CVE-2013-3540?

CVE-2013-3540 is a medium-severity vulnerability in n/a, published on 4 Oct 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in cgi-bin/admin/usrgrp.cgi in AirLive POE2600HD, POE250HD, POE200HD, OD-325HD, OD-2025HD, OD-2060HD, POE100HD, and possibly other camera models allows remote attackers to hijack the authentication of administrators for requests that add users.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 6 products.


Products: Ovislink Airlive Od-2025hd, Ovislink Airlive Od-2060hd, Ovislink Airlive Poe100hd, Ovislink Airlive Poe200hd, Ovislink Airlive Poe250hd, Ovislink Airlive Poe2600hd.

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

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

## Is CVE-2013-3540 being exploited?

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

Public exploit code:

- Airlive IP Cameras - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-3687](https://insights.sbomify.com/CVE-2013-3687/): Information disclosure in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-3540 is a medium-severity vulnerability in n/a, published on 4 Oct 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-3540 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-3540/ (Markdown: https://insights.sbomify.com/CVE-2013-3540/index.md)
```

## Sources

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

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