# CVE-2007-6763: Auth bypass in n/a

> Attackers can access protected resources after logout by using browser navigation buttons due to improper session termination handling.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2019
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9v4f-qv93-x5wc

## What is CVE-2007-6763?

CVE-2007-6763 is a high-severity authentication bypass vulnerability in n/a, published on 31 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAS Drug Development (SDD) before 32DRG02 mishandles logout actions, which allows a user (who was previously logged in) to access resources by pressing a back or forward button in a web browser.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2007-6763?

It affects 1 product.


Products: Sas Sas Drug Development.

## How do I fix CVE-2007-6763?

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

## Is CVE-2007-6763 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-6763 and fix it if it is affected.

What it is: CVE-2007-6763 is a high-severity authentication bypass vulnerability in n/a, published on 31 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-6763 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-2007-6763/ (Markdown: https://insights.sbomify.com/CVE-2007-6763/index.md)
```

## Sources

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

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