CVE-2024-22113
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpen redirect vulnerability in Access analysis CGI An-Analyzer released in 2023 December 31 and earlier allows a remote unauthenticated attacker to redirect users to arbitrary websites and conduct phishing attacks via a specially crafted URL.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpen redirect vulnerability in Access analysis CGI An-Analyzer allows a remote unauthenticated attacker to craft malicious URLs that redirect users to arbitrary external websites for phishing attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2023-12-31CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the An-Analyzer CGI scriptSearch the web server for CGI files named 'analyzer', 'an-analyzer', or similar in the cgi-bin directory. Common paths include /cgi-bin/ or /cgi/ folders. Look for files with .cgi or .pl extensions related to access analysis.Affected if The An-Analyzer CGI script is present on the server
-
Identify installed versionOpen the An-Analyzer CGI script in a text editor and look for version strings, release dates, or build numbers in the code comments, headers, or configuration sections. Alternatively, access the CGI directly and check any displayed version information or error messages.Affected if The version is dated December 31, 2023 or earlier, or no version is displayed (indicating an old installation)
-
Test for redirect parameter vulnerabilitySend a crafted request to the An-Analyzer CGI URL with an external domain in a redirect-type parameter. Common parameter names to test include 'url', 'redirect', 'next', 'dest', or 'goto'. Example: curl -I 'http://TARGET/cgi-bin/an-analyzer?url=http://malicious.example.com'. Check the Location header in the response.Affected if The response includes a Location header pointing to the external domain provided in the request, confirming the open redirect is present
If the An-Analyzer CGI exists, the version is from 2023 or earlier, and the redirect test shows external URLs are accepted, the environment is affected by CVE-2024-22113.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate An-Analyzer to a version released after December 31, 2023, or implement URL validation to restrict redirect destinations to internal paths only.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22113 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-22113 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data