CVE-2011-1008 Scrips_Overlay.pm in Best Practical Solutions RT before 3.8.9 does not properly restrict access to a TicketObj in a Scrip after a CurrentUse
Medium 4.0
Published
Updated
Check this codebase for CVE-2011-1008 and fix it if it is affected.
What it is: CVE-2011-1008 is a medium-severity vulnerability in n/a, published on 28 Feb 2011.
Exploitation: There is no known exploitation of CVE-2011-1008 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-2011-1008/ (Markdown: https://insights.sbomify.com/CVE-2011-1008/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2011-1008?
CVE-2011-1008 is a medium-severity vulnerability in n/a, published on 28 Feb 2011.
Official description
Scrips_Overlay.pm in Best Practical Solutions RT before 3.8.9 does not properly restrict access to a TicketObj in a Scrip after a CurrentUser change, which allows remote authenticated users to obtain sensitive information via unspecified vectors, as demonstrated by custom-field value information, related to SQL logging.
Weakness: CWE-264
Which versions are affected by CVE-2011-1008?
It affects 1 product.
Products include Bestpractical Rt.
How do I fix CVE-2011-1008?
No fix has been published for CVE-2011-1008 yet. Limit exposure of the affected software until one is available.
Is CVE-2011-1008 being exploited?
There is no known exploitation of CVE-2011-1008 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-pprg-q2gm-jrhj.