Skip to content

Updated encryption key file path to jfrog-home dir instead of jenkins…#141

Merged
naveenku-jfrog merged 5 commits intojfrog:mainfrom
naveenku-jfrog:fix/RTECO-857-Jfrog-Jenkins-Plugin-latest-version-is-stopped-working
Feb 19, 2026
Merged

Updated encryption key file path to jfrog-home dir instead of jenkins…#141
naveenku-jfrog merged 5 commits intojfrog:mainfrom
naveenku-jfrog:fix/RTECO-857-Jfrog-Jenkins-Plugin-latest-version-is-stopped-working

Conversation

@naveenku-jfrog
Copy link

@naveenku-jfrog naveenku-jfrog commented Feb 19, 2026

Description:

What is the change?
Store encrypted key in a file under JfrogHomeDir

Why is this fix?
encrypted key file was stored in Jenkins Workspace which is not accessible and failing with failed to stat encryption key file

@bhanurp bhanurp added the bug Something isn't working label Feb 19, 2026
@github-actions
Copy link

🚨 Frogbot scanned this pull request and found the below:

📗 Scan Summary

  • Frogbot scanned for vulnerabilities and found 1 issues
Scan Category Status Security Issues
Software Composition Analysis ℹ️ Not Scanned -
Contextual Analysis ✅ Done -
Static Application Security Testing (SAST) ✅ Done
1 Issues Found 1 Low
Secrets ✅ Done -
Infrastructure as Code (IaC) ✅ Done Not Found

}

// Add HTTP or HTTPS protocol according to the port
String proxyUrl = proxyConfiguration.port == 443 ? "https://" : "http://";

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Static Application Security Testing (SAST) Vulnerability

Severity Finding
low
Low
Detected usage of communication methods lacking encryption.
Full description

Vulnerability Details

Rule ID: java-insecure-protocol

Overview

Using insecure protocols—such as HTTP, FTP, or LDAP—can expose sensitive
data during transmission, making it vulnerable to eavesdropping and man-in-the-middle
attacks. Secure protocols like HTTPS and FTPS should be used to ensure data
encryption during communication.

Vulnerable example

In this example, the application uses insecure protocols to communicate,
taking the protocol type from hardcoded strings.

import java.io.IOException;
import java.net.URL;
import java.net.URLConnection;

public class insecure_protocol_vuln {

    public void connectToFrogService(String server) throws IOException {
        String insecureHttpProtocol = "http://"; // Insecure protocol
        String url = insecureHttpProtocol + server + "/frogEndpoint";
        URL obj = new URL(url);
        URLConnection conn = obj.openConnection(); // Vulnerable: Insecure protocol
        conn.connect();
    }
}

Remediation

To mitigate the use of insecure protocols, replace them with secure alternatives
such as HTTPS or FTPS.

import java.io.IOException;
import java.net.URL;
import java.net.URLConnection;
import javax.net.ssl.HttpsURLConnection;

public class insecure_protocol_safe {

    public void connectToFrogService(String server) throws IOException {
        String secureHttpProtocol = "https://"; // Secure protocol
        String url = secureHttpProtocol + server + "/frogEndpoint";
        URL obj = new URL(url);
        HttpsURLConnection conn = (HttpsURLConnection) obj.openConnection(); // Safe: Secure protocol
        conn.connect();
    }
}

<br></details>

---
<div align='center'>

[🐸 JFrog Frogbot](https://jfrog.com/help/r/jfrog-security-user-guide/shift-left-on-security/frogbot)

</div>

@naveenku-jfrog naveenku-jfrog merged commit 3d21be0 into jfrog:main Feb 19, 2026
2 of 3 checks passed
bhanurp pushed a commit to bhanurp/jenkins-jfrog-plugin that referenced this pull request Mar 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants