CVE-2025-58335
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 · uneditedIn JetBrains Junie before 252.284.66, 251.284.66, 243.284.66, 252.284.61, 251.284.61, 243.284.61, 252.284.50, 252.284.54, 251.284.54, 251.284.50, 243.284.54, 243.284.50 information disclosure was possible via search_project function
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 confidenceJetBrains Junie before the specified versions contains an information disclosure vulnerability in the search_project function. The CVSS 7.5 score indicates the exposed information could have significant impact, likely exposing sensitive project data or credentials through improper access controls on the search functionality.
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< 243.284.50>= 251.72.165, < 251.284.50>= 252.204.139, < 252.284.50CVSS 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 Junie versionAccess the Junie application and navigate to Help > About, or check the version from the startup logs or installed package information. If using a CLI tool, run: junie --version or check the binary metadata.Affected if The installed version falls within < 243.284.50, >= 251.72.165 and < 251.284.50, or >= 252.204.139 and < 252.284.50.
-
Verify search_project function accessibilityLocate the Junie configuration files or API endpoints that expose the search_project function. Check if the function is accessible via web API, CLI, or internal service call.Affected if The search_project function is exposed without proper authorization controls, or the endpoint is reachable without authentication.
-
Review access control configurationExamine Junie's authentication and authorization settings in the configuration files (typically in conf/, config/, or similar directories). Look for settings that control access to search operations.Affected if Authentication is disabled or the search_project function lacks role-based or user-based access restrictions.
-
Inspect API access logs for search_projectReview Junie's access logs, audit logs, or API request logs for any calls to the search_project endpoint. Look for requests that may have accessed data outside the caller's authorized scope.Affected if Logs show search_project calls returning data belonging to other users or projects without proper authorization checks.
You are affected if your Junie version is below 243.284.50, between 251.72.165-251.284.50, or between 252.204.139-252.284.50 AND the search_project function is accessible in your environment.
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 · scoped243.284.50251.284.50252.284.50
Update JetBrains Junie to the latest patched version beyond 252.284.66/251.284.66/243.284.66. Review the search_project function implementation for improper authorization checks and ensure authenticated users can only access data they're permitted to view.
Upgrade to Junie 243.284.66 (for 243.x branch), 251.284.66 (for 251.x branch), or 252.284.66 (for 252.x branch) or later
- 1. Identify the major version branch of Junie currently in use (243.x, 251.x, or 252.x)
- 2. Check the currently installed version: go to Junie > About Junie (or Help > About)
- 3. For 243.x branch: upgrade to version 243.284.66 or later
- 4. For 251.x branch: upgrade to version 251.284.66 or later
- 5. For 252.x branch: upgrade to version 252.284.66 or later
- 6. Verify the upgrade was successful by checking Help > About shows the fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58335 — 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-2025-58335 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