[ 
https://issues.apache.org/jira/browse/HIVE-30243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stamatis Zampetakis updated HIVE-30243:
---------------------------------------
    Security:     (was: Non-Public)

> Deprecated TLS 1.1 Protocol and Legacy CBC Cipher Suite Supported on 
> ci.hive.apache.org
> ---------------------------------------------------------------------------------------
>
>                 Key: HIVE-30243
>                 URL: https://issues.apache.org/jira/browse/HIVE-30243
>             Project: Hive
>          Issue Type: Bug
>          Components: Build Infrastructure
>            Reporter: Stamatis Zampetakis
>            Assignee: Stamatis Zampetakis
>            Priority: Major
>             Fix For: Not Applicable
>
>
> h3. Vulnerability Summary
> Affected Host: ci.hive.apache.org
> Affected Port: 443
> Protocol: TLS 1.1
> Detected Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
> Vulnerability Type: Deprecated TLS Protocol / Legacy Cipher Suite Support
> Severity: Low (but can lead to higher impact if combined with other factors)
> The HTTPS endpoint at ci.hive.apache.org was detected supporting TLS 1.1 and 
> the legacy CBC-based cipher suite TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA.
> h3. Vulnerability Description
> TLS 1.1 is formally deprecated under RFC 8996. Its continued availability 
> allows clients to establish encrypted connections using an outdated protocol 
> version that lacks the security improvements and protections expected from 
> modern TLS deployments.
> The detected cipher suite consists of:
> ECDHE: Provides ephemeral key exchange and forward secrecy.
> AES-128-CBC: Uses the legacy Cipher Block Chaining encryption mode.
> SHA-1: Used for HMAC message authentication, not necessarily for certificate 
> signatures.
> Although AES-128 and ECDHE are not inherently broken, CBC-based cipher suites 
> are legacy options. Modern TLS deployments should prioritize TLS 1.2 and TLS 
> 1.3 with authenticated encryption (AEAD) cipher suites, such as AES-GCM or 
> ChaCha20-Poly1305.
> The scanner finding demonstrates protocol and cipher-suite availability; it 
> does not independently establish that the endpoint is exploitable.
> h3. Security Impact
> Security Risks
> Deprecated Protocol Exposure: Clients may establish connections using an 
> outdated TLS version.
> Legacy Cryptographic Configuration: CBC-based cipher suites have a more 
> complex security history than modern AEAD alternatives.
> Increased Attack Surface: Supporting outdated protocols creates unnecessary 
> cryptographic compatibility and maintenance overhead.
> Downgrade Exposure: Legacy protocol availability may increase exposure when 
> combined with other weaknesses or insecure client configurations.
> Compliance Risks
> TLS 1.1 support may conflict with modern organizational security baselines 
> and applicable security requirements that mandate current TLS versions.
> Trust and Reputation
> Maintaining outdated cryptographic configurations may negatively affect 
> external security assessments and confidence in the service's security 
> posture.
> h3. Steps to Reproduce / Verify
> Step 1: Test TLS 1.1 Using OpenSSL
> Execute:
> openssl s_client -connect ci.hive.apache.org:443 -servername 
> ci.hive.apache.org -tls1_1
> Observed Result: A successful handshake negotiating TLS 1.1 confirms that the 
> endpoint accepts the deprecated protocol.
> Expected Result: The server should reject TLS 1.1 connections.
> Note: Local OpenSSL security policies may independently prevent TLS 1.1 
> connections, even when the remote endpoint supports them.
> Step 2: Enumerate Supported TLS Versions and Cipher Suites
> Execute:
> nmap -p 443 --script ssl-enum-ciphers ci.hive.apache.org
> Observed Result: The scan identifies TLS 1.1 and the following cipher suite:
> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
> Expected Result: TLS 1.1 should not be available, and only approved modern 
> TLS configurations should remain enabled.
> Step 3: Verify Using Nuclei
> Execute:
> nuclei -u [https://ci.hive.apache.org|https://ci.hive.apache.org/] -tags ssl
> Observed Result: Nuclei reports TLS 1.1 support with the identified CBC 
> cipher suite.
> h3. Remediation & Recommendations
> Review the TLS configuration of the HTTPS endpoint serving ci.hive.apache.org.
> Disable TLS 1.1 so that clients cannot negotiate the deprecated protocol.
> Retain TLS 1.2 and TLS 1.3, subject to compatibility requirements.
> Prefer modern AEAD cipher suites such as AES-GCM and ChaCha20-Poly1305.
> Review and remove unnecessary legacy CBC cipher suites.
> If TLS termination occurs through a CDN, reverse proxy, load balancer, or 
> managed infrastructure, apply the changes at the actual TLS termination point.
> Re-test using Nmap, OpenSSL, and Nuclei to confirm that TLS 1.1 is no longer 
> negotiable.
> h3. Evidence
> Finding:
> [weak-cipher-suites:tls-1.1] [ssl] [low] ci.hive.apache.org:443 ["[tls11 
> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA]"]
> The scanner identifies TLS 1.1 support and the legacy CBC cipher suite on 
> port 443.
> h3. References
> RFC 8996 – Deprecating TLS 1.0 and TLS 1.1
> [https://datatracker.ietf.org/doc/html/rfc8996]
> OWASP Transport Layer Security Cheat Sheet
> [https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html]
> Mozilla SSL Configuration Generator
> [https://ssl-config.mozilla.org/]
> NIST SP 800-52 Rev. 2 – Guidelines for the Selection, Configuration, and Use 
> of TLS Implementations
> [https://csrc.nist.gov/pubs/sp/800/52/r2/final]



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to