CVE-2024-26309
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 · uneditedArcher Platform 6.x before 6.14 P2 HF2 (6.14.0.2.2) contains a sensitive information disclosure vulnerability. An unauthenticated attacker could potentially obtain access to sensitive information via an internal 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 · moderate confidenceThis is an unauthenticated information disclosure vulnerability in RSA Archer Platform where an internal/diagnostic URL is accessible without authentication, potentially exposing sensitive system information to remote attackers.
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>= 6.3.0.0, < 6.14.0.2.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Determine installed RSA Archer Platform versionLog into the Archer web interface and navigate to About/Version information page, or check the installation directory for version manifest filesAffected if version is 6.3.0.0 or higher but below 6.14.0.2.2
-
Identify diagnostic URL endpointsReview web server configuration files (web.config or IIS settings) for custom handler mappings or URL rewrite rules that point to internal/diagnostic pathsAffected if diagnostic or internal API endpoints are configured and exposed
-
Test unauthenticated access to diagnostic URLsUsing a web browser or curl tool, attempt to access common diagnostic paths such as /内部的URL或/诊断路径 without providing credentialsAffected if the URL returns sensitive system information without requiring authentication
-
Verify network access controlsReview firewall or network segmentation rules to determine if the Archer server's diagnostic endpoints are accessible from untrusted/networked segmentsAffected if diagnostic URLs are reachable from networks outside the trusted internal zone
Environment is affected if running Archer Platform version 6.3.0.0 through 6.14.0.2.1 and internal/diagnostic URLs are accessible without authentication from untrusted network segments
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.
dbcve · scoped6.14.0.2.2
Apply the vendor patch (6.14 P2 HF2 or later) and review network segmentation to restrict access to internal URLs from untrusted networks.
Archer Platform 6.14 P2 HF2 (6.14.0.2.2) or later
- Identify your current Archer Platform version by accessing the Archer Control Panel/Administration Console
- Download the Archer 6.14 P2 HF2 (version 6.14.0.2.2) or a later stable release from the RSA Archer customer portal
- Review the Archer 6.14 P2 HF2 release notes and installation instructions
- Execute the upgrade following the standard Archer upgrade procedure, which typically includes: backing up the current installation, stopping services, running the installer, and verifying the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26309 — 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-26309 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