CVE-2023-45705
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 · uneditedAn administrative user of WebReports may perform a Server Side Request Forgery (SSRF) exploit through SMTP configuration options.
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 confidenceWebReports contains an SSRF vulnerability where an authenticated administrative user can abuse SMTP configuration options to make the server perform arbitrary HTTP requests to internal or external resources. This could allow enumeration of internal services, access to cloud metadata endpoints, or pivoting to internal infrastructure.
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>= 10, < 10.0.11>= 11.0.0, < 11.0.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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify the installed Bigfix Platform versionAccess the Bigfix console or use the relevant version query command for the Bigfix Platform installation. Common methods include checking the console's About section or querying the Bigfix server via its administration interface.Affected if The installed version falls within the affected ranges: 10.x prior to 10.0.11, or 11.x prior to 11.0.2.
-
Confirm WebReports component is installed and enabledVerify that the WebReports component is present in the Bigfix Platform deployment. This is typically accessible through the Bigfix console or administration interface under the WebReports section.Affected if WebReports is installed and accessible.
-
Verify SMTP configuration is accessible to administrative usersCheck the WebReports administration interface for SMTP configuration options. Look for settings that allow input of URLs or hosts for SMTP server configuration.Affected if SMTP configuration fields allow direct URL or host input and are accessible to authenticated administrative users.
-
Confirm administrative user accounts exist with access to WebReportsReview the user accounts configured with administrative privileges in WebReports. Check if any authenticated administrator can access the SMTP configuration settings.Affected if Authenticated administrative users have access to the WebReports SMTP configuration interface.
The environment is affected if the Bigfix Platform version is within the vulnerable ranges (10.x < 10.0.11 or 11.x < 11.0.2) AND WebReports with SMTP configuration is accessible to authenticated administrative users.
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 · scoped10.0.1111.0.2
Implement strict allowlist validation for all URLs/hosts entered in SMTP configuration fields, restrict outbound network access from the application server, and consider disabling direct URL input in favor of pre-configured SMTP server options.
Upgrade to BigFix Platform 10.0.11 (for 10.x versions) or 11.0.2 (for 11.x versions) or later respective major version
- Identify the current BigFix Platform version by checking the installation or console
- For versions 10.x (>=10.0.0 and <10.0.11): Plan upgrade to version 10.0.11 or later
- For versions 11.x (>=11.0.0 and <11.0.2): Plan upgrade to version 11.0.2 or later
- Create a full backup of the BigFix database and configuration files before upgrading
- Follow HCL BigFix upgrade documentation to perform the version upgrade
- After upgrade, verify the WebReports SMTP configuration is still intact and functional
- Confirm the vulnerability is remediated by testing that the SSRF vector through SMTP configuration is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45705 — 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-2023-45705 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